Although, it looks like you can not have both the classic settings.py and django-constance at the same time, right ?
It would be nice to be able to have both backend, one for config var that hardly changes and one for settings that can by customize by someone not versed in IT through an admin page.
I would assume that this module is using redis's pub/sub capabilities to push configuration out to django app servers whereas creating an extra_settings table would likely require polling.
I don't know about "recommended over" but it may perhaps be "a more advanced way to". It depends upon your needs.
Lets say that you're running a service that has 20 servers running a Django app, and you want to be able to update the configuration for these apps in real time. Can this be done easily using environment variables?
(Serious question. I haven't actually thought much about this, but my instinct is that it will be more difficult.)
11 comments
[ 2.7 ms ] story [ 28.3 ms ] thread(I know it's not for caching because a database cache backend is mentioned separately).
Although, it looks like you can not have both the classic settings.py and django-constance at the same time, right ?
It would be nice to be able to have both backend, one for config var that hardly changes and one for settings that can by customize by someone not versed in IT through an admin page.
I'm probably missing something.
Lets say that you're running a service that has 20 servers running a Django app, and you want to be able to update the configuration for these apps in real time. Can this be done easily using environment variables?
(Serious question. I haven't actually thought much about this, but my instinct is that it will be more difficult.)
http://zookeeper.apache.org/
(I'm experimenting with django-dynamicsites-lite to do this but, while it appears to work, it is awfully hacky.)