....
I see configurable settings, like those in the settings module, as code
settings, and those you would put in the DB as
user customizable settings. The former are meant to be changed by developers
and sys admins, and the latter by website
users. In my opinion settings module changes are mostly related to staging or
performance rather than user oriented.
Apart from there are a number of interesting Django apps in Djangopackages [1]
that allow you to put your settings in
the DB.
[1] -> https://www.djangopackages.com/grids/g/configuration/
Regards
Thank you for this link. Unfortunately the feature "data store" is not
evaluated up to now. But I created
a feature request: https://github.com/pydanny/djangopackages/issues/293
Thomas
--
Thomas Güttler
http://thomas-guettler.de/
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/542A5407.1020500%40tbz-pariv.de.
For more options, visit https://groups.google.com/d/optout.
