5π
The local_settings.py
is only for on your local development system where it extends settings.py
. On your deployment server, settings.py
is used only without local_settings.py
.
One recommendation is that local_settings.py
is not included in your repository, so that each developer can have their own and so that it is not used on the deployment server.
Checkout these articles for more information:
0π
The idea is that settings.py
contains all the settings you actually need to run your project. local_settings.py
is for if you need to override any of them locally, for instance in development. For example, you might have different database passwords, or template paths, etc.
The answer to your question is to put new settings into settings.py
, though.
- [Django]-Can I query a secondary database from Django without ORM?
- [Django]-Postgres connection details in django and chef
- [Django]-Wagtail / Hallo.js β Adding plugins but modified content is not saved
- [Django]-Django rest framework : How to download image with this image send directly in the body
- [Django]-Django StreamingHttpResponse into a Template