Skip to content
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

Use prettyconf instead separated settings files #12

Open
raelmax opened this issue Oct 29, 2017 · 1 comment · May be fixed by #14
Open

Use prettyconf instead separated settings files #12

raelmax opened this issue Oct 29, 2017 · 1 comment · May be fixed by #14
Assignees

Comments

@raelmax
Copy link

raelmax commented Oct 29, 2017

I think use environment variables it's a better way to separate development and production settings and the prettyconf project can be useful in this implementation. I can do this improvement, what you think?

@raelmax raelmax changed the title User prettyconf instead separated settings files Use prettyconf instead separated settings files Oct 29, 2017
@hersonls
Copy link
Owner

@raelmax it will be awesome!

I believe the default settings for frontend paths, like static and templates can come from frontend app ( which will be a external package soon ).

So, if you need to set default values for these settings backend/backend/settings/develop.py#L3-L24, lets think about move the default values to backend/apps/frontend, some conf.py file for example.

@hersonls hersonls assigned hersonls and raelmax and unassigned hersonls Oct 30, 2017
@bgomes bgomes linked a pull request Nov 1, 2017 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants