- June 9, 2009
- -3 (after 5 ratings)
If you have a production, staging, testing and development environment, you might want to have a global checked in (in your version control system) settings.py for production + a local settings.py to override various settings (like database connection).
It's also good for development, since developers don't - by incident - commit to the production settings.py, since they can use their local settings, that should be ignored (.cvsignore, .svnignore or similar).
1 2 3 4
try: from settings_local import * except: pass
More like this
- Load a local settings file for dev/test environments by menendez 7 years, 6 months ago
- Keep settings.py in version control safely by mboersma 8 years, 11 months ago
- Read settings from local_settings.py by statico 6 years ago
- Django Settings Splitter & Local Settings loader by rudude 1 year, 11 months ago
- Different approach to local settings.py by jokull 7 years, 12 months ago