django-blog VS python-dotenv

git remote add rail https://github.com/Mr-Destructive/django-blog/tree/railway git push rail railway

We assume you already have a Django project configured with some basic URLs, views and templates or static files as per your project and requirements, for this tutorial I will be using the simple blog application from my previous Django tutorials as a reference. You can follow along with my Django Basics series and refer to the Blog Application project on GitHub.

For any references, you can take a look at the GitHub repository for the CRUD API in pure Django.

I personally just use .env to keep api keys

similar to dotenv, I like this object oriented approach though.

Are you working on a Python project that uses pdm for dependency management and dotenv for local environment variable and secrets management? Do you find it frustrating when CLI tools like pgcli don't automatically pick up your .env file, forcing you to resort to npm install -g dotenv-cli? I've got a more convenient solution for you!

Similarly, I use python-dotenv which reads environment variables, or variables set in a .env file. Then in your settings.py file you can do things like:

Locally you may want to use a .env file that is also in .gitignore and python-dotenv to auto activate them. Also having an .env.template is also a good idea to help others working on the project know what they need to set in order for things to work.

But there's no web UI to set them for your local dev version. But there are various Python modules that will read environment variables from a file named .env. I like https://github.com/theskumar/python-dotenv myself. So try using that - create a .env file for your local dev site and use dotenv instead of os.getenv() to read the environment variables.

python-dotenv