The topic of Stop Putting Everything in .env — Runtime Config for Django is currently the subject of lively debate — readers and analysts are keeping a close eye on developments.
This is taking place in a dynamic environment: companies’ decisions and competitors’ reactions can quickly change the picture.
Here’s the problem that led me to build it. We all tend to bloat the settings.py and .env files to store all these secrets and other API URLs for 3rd-party integrations. This approach requires the server restart on each change to .env file, and also this is not a scalable solution.
django-sysconfig is a schema-driven database-backed typed runtime configuration app for Django. This app has in-built cache support (using Django Cache Framework) with a simple Admin UI to allow non-IT admins to easily manage the project configurations.
This app is built to be extended from the core. You don’t like the admin UI. Make your own the core config API and simple templates. Need new validators or new config Field types? Create your own very easily.
I’ve recently released the v1.0.0 to PyPi. Feel free to try it out. Would love your feedback on this.
GitHub Repo: https://github.com/krishnamodepalli/django-sysconfig
Docs: https://krishnamodepalli.github.io/django-sysconfig/
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment’s permalink.
For further actions, you may consider blocking this person and/or reporting abuse
Built on Forem — the open source software that powers DEV and other inclusive communities.
Why it matters
News like this often changes audience expectations and competitors’ plans.
When one player makes a move, others usually react — it is worth reading the event in context.
What to look out for next
The full picture will become clear in time, but the headline already shows the dynamics of the industry.
Further statements and user reactions will add to the story.