python-decouple VS django-heroku

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.

Surprised nobody here has mentioned WhiteNoise yet. Use the django-heroku package and WhiteNoise and you can serve all your static files directly from Heroku, no need for S3. It's pretty much magic, just follow the installation instructions for django-heroku, it has WhiteNoise as a dependency. If you want better performance then stick a CDN like CloudFlare in front and it will take care of caching all the static files. Heroku themselves recommend using WhiteNoise, the django-heroku package just does all the config for you.

django-heroku: We have to Configure Django app for Heroku. This lib provides settings, logging and test runner configurations.

But I'm not sure the python version is the issue here. This issue looks similar to yours: https://github.com/heroku/django-heroku/issues/39

And Its from Heroku Docs, and last maintained 3 years ago..

You should probably avoid using the Django-Heroku package at this point. The last substantive code commit is nearing three years ago. So I would try removing the django_heroku.settings(locals()) line. You would also need to insert new settings to use PostgreSQL as your database. On Heroku, this is best accomplished with [dj-database-url](https://github.com/jacobian/dj-database-url), which was a dependency of Django-Heroku but is still updated. There are many ways to set it up, but I typically use:

I find it very peculiar that Heroku's own documentation suggest using django-heroku although the repository is in archive mode.