django-split-settings VS python-decouple

Large settings.py file! Even close to 1 mg volume! This error often misleads you and other developers who are reading your code. Try not to make your settings.py file too large. Delete the comments first, then try using the split_settings tool to separate the project settings.

I'm using https://github.com/sobolevn/django-split-settings

Use a library likepython-decouple to separate secrets like DB_xxx, SECRET_KEY, etc. Then follow this deploy to Digital Ocean. It might be slightly out of date, but I'm pretty sure it'll work just fine.

Documentation for python decouple: https://github.com/henriquebastos/python-decouple/ Documentation for smtplib: https://docs.python.org/3/library/smtplib.html

I wish Django was more "12-factor" compliant by default. Reading secrets from environment variables should be a first-class citizen and it's not. I typically use python-decouple (https://github.com/henriquebastos/python-decouple/) for that but it would be great to have it as default.

python-decouple: We can remove sensitive data like SEECERT_KEY, DB Password from settings.py and add it in .env file.

https://github.com/henriquebastos/python-decouple

I’ve been using this for a while and it seems to solve this pretty well.

First, about the libraries that will be used, there will be three: Python Requests, json and Python Decouple. Python Requests will be responsible for carrying out the HTTP requests, json will help handle the responses obtained for the .json format, and the Python Decouple library will assist in the separation of the authentication from what is in the code.