having an application specific settings.py is a nice idea, in our world. In the real world websites seem to be managed by non-technical people... and ultimately we're not just building these applications for technologically "gifted" people. Settings should be defined with the admin for certain things... how many blog items or gallery images would you like per page? this shouldn't require a call to "IT support" or granting someone server access to change these settings when they wish (then call IT support when they screw it up)
what are our options to grant admin based settings? Obviously a model called settings with perhaps it's own admin template to only allow/ show a single entry into this model/db is possible. But should it really warrant an additional database call every time the page is loaded to grab the settings(lets ignore caching for the moment)? How about an xml file that is editable by the admin? seems like a valid option to have a config.xml associated with a project and to have the admin site access to it, i presume a feature like this would require a hook into the admin site. any input, ideas, experiences? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
