Stop Putting Everything in .env — Runtime Config for Django

Hello all! 👋 TL;DR I created a runtime configuration Django app called django-sysconfig . 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. The 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. Some features of this app: Validations (email, url, ip, port, hostname, min-max, regex, etc. Each config value will be validated before saving to DB) A clean Admin UI to manage configurations. Schema based config. Your schema updates as your app grows and is distributed across your apps instead of a single place) on_save callbacks for each config (helpful f