-
Notifications
You must be signed in to change notification settings - Fork 422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PostgreSQL by default ? #3
Comments
Yes, I believe that makes the most sense to have kinto persist on disk by default. Redis / Memory are too volatile to make them defaults here. |
It depends what default means, for me default are to help the dev to get started. Not default configuration for production. Maybe the answer is not the same for kinto and cliquet on this. But IMHO the default should be something easier to setup than postgresql. |
Btw on defaut Redis configuration, persistence on disk is activated. |
If we need to differentiate between defaults for the devs and defaults for prod, then we probably should have two different set of configuration files. I don't consider postgres to be something harder than postgres to install (but yes, that's a personal thing I believe). So, even if it is (hard to install), we should document how to install it (with a docker, yo). I wasn't aware for redis persisting on disk by default, cool!
|
PostgreSQL is a lot more easy to install than Redis (see docs), but since we don't have any other session backend implementation, using psql by default does not prevent us from running Redis! We could consider defaulting to PostgreSQL once we have session backend running on it :) |
Since the default test database is postgres in cliquet, there is no database creation step |
Use postgreSQL per default. fix #3 r @leplatrem
cliquet[postgresql]
in requirementsThe text was updated successfully, but these errors were encountered: