3 ms·
how settings.py gets so large is not only a valid problem in of itself, but also symptom of another problem: it is hard (or at least not obvious) to have confi
by rguzman 14y ago
how settings.py gets so large is not only a valid problem in of itself, but also symptom of another problem: it is hard (or at least not obvious) to have configuration that can be changed from the admin.
i've considered implementing something that works similarly to the sites contrib app for this, but it always seems that for it to be useful it needs to hook into django internals more than apps "are supposed to".
- est 14y ago> it is hard (or at least not obvious) to have configuration that can be changed from the admin. You are doing settings.py wrong. You should have your own SiteConfig model stored and manipulated in a db. Settings.py is for static, persistent attributes, not for site-wide variables which need auditing or updated from time to time.