Thanks for the answer. In particular I'm wondering about apps that will be shared by several projects. The default_settings.py would then be the values of the settings if the projects don't override these settings in their DJANGO_SETTINGS_MODULEs. Effectively I'm planning on using something like django.conf.settings but where the defaults are in the application itself rather than in django.conf.global_settings. It sounds like there's no convention for something like this.
On Jun 5, 10:46 pm, Ben Davis <[email protected]> wrote: > I'm not sure that there's a real "standard" for it, but that's more or less > what I've done for my projects, except my multi-environment setup looks > like this: > > settings/ > __init__.py > defaults.py > development.py > staging.py > production.py > > all my default/common settings go in defaults.py, and for each environment > (development, staging, production) I have "from defaults import *" at the > top. I then set DJANGO_SETTINGS_MODULE to one of the appropriate modules, > eg: "settings.development". I'm not sure how standard that is, but it > works well for me. > > On Fri, Jun 5, 2009 at 11:39 PM, ben <[email protected]> wrote: > > > I'm wondering if a convention exists for dealing with applications > > settings. I'm thinking of having the default settings to be > > specified in my application in a default_settings.py file but be > > overridden by any values in DJANGO_SETTINGS_MODULE. I can do this > > easily enough, but it feels like something that might be already > > standardised. Does a convention exist, and if so what is it? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
