DownloadOrganize Django settings into multiple files and directories. Easily override and modify settings. Use wildcards in settings file paths and mark settings files as optional. Managing Django’s settings might be tricky. There are severals issues which are encountered by any Django developer along the way. First one is caused by the default project structure. Django clearly offers us a single settings.py file. It seams reasonable at the first glance. And it is actually easy to use just after the start. But when it comes to the real-world it only causes misunderstanding and frustration. At some point, you will need to put some kind of personal settings in the main file: certificate paths, your username or password, database connection, etc. But putting your user-specific values inside the common settings is a bad practice. Other developers would have other settings, and it would just not work for all of you.
Features
- Replace your existing settings.py with a list of components that make up your Django settings
- Preferably create a settings package that contains all the files
- The local context is passed on to each file
- Note that files are included in the order that glob returns them
- You can modify common settings in environment settings simply importing them
- This package has no dependencies itself
Project Samples
