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.

Sign up for GitHub

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

Jump to bottom

Separate settings file for dev, production and testing #3

Closed
42hrs opened this issue Dec 22, 2014 · 2 comments
Closed

Separate settings file for dev, production and testing #3

42hrs opened this issue Dec 22, 2014 · 2 comments
Labels
enhancement

Comments

@42hrs
Copy link

42hrs commented Dec 22, 2014

Is there any design decision restricting from maintaining separate settings file for production and development? I usually have prod.py and dev.py both importing common settings from base.py, which all reside inside a settings module. If there're are no objection, would a PR on this be accepted?
@arocks
Copy link
Owner

arocks commented Jan 1, 2015

It was done for simplicity. A PR would be welcome :)

@arocks arocks mentioned this issue Feb 17, 2015
Closed
@arocks
Copy link
Owner

arocks commented Feb 21, 2015

Implemented in Edge v2.0 :)

@arocks arocks closed this as completed Feb 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arocks @42hrs