Last updated 1 year ago by Nikita Sobolevdjango
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. The most known hack for this situation is local_settings.py.