This link and the comments suggest some good stuff... particularly the comment from Malcolm and the original post.
http://www.protocolostomy.com/2009/08/17/django-settings-in-dev-and-production-why-the-hoops/ On Fri, Sep 24, 2010 at 10:01 AM, David P. Novakovic <davidnovako...@gmail.com> wrote: > The thing is, in production mode you normally have to define where > your settings are anyway, so you pass the unusual settings file name > there, and just use the regular settings.py for your development. > > So then you are passing the settings configuration information once in > the production server's configuration, not every time you run your > development server. > > I think people with any decent sized project have addressed this issue > in their own way that suits their own needs. > > For example we have lots of settings files and just import the > relevant settings into a final file. > > For testing I do what i mentioned in my previous email. > > Like anything on here, you need to ask whether what you are suggesting > would actually be better off as part of the core or if it works just > fine as something that people can choose to use themselves... > > I think most people use whatever system they are happy with and it > doesn't get in the way of deployment/development. Thus this fails to > meet one of the critical requirements for consideration for inclusion > into core. > > D > > On Fri, Sep 24, 2010 at 9:27 AM, Yo-Yo Ma <baxterstock...@gmail.com> wrote: >> Thanks David, but I'm talking about having something built in. For >> instance, passing a variable to the "Development" server to tell it >> you're in "Development" seems a bit redundant, no? >> >> On Sep 23, 3:39 pm, "David P. Novakovic" <davidnovako...@gmail.com> >> wrote: >>> As for running different configs: >>> >>> manage.py runserver --settings=settings_test >>> >>> etc.. >>> >>> On Fri, Sep 24, 2010 at 7:25 AM, Jacob Kaplan-Moss <ja...@jacobian.org> >>> wrote: >>> > On Thu, Sep 23, 2010 at 3:33 PM, Yo-Yo Ma <baxterstock...@gmail.com> >>> > wrote: >>> >> I'm simply proposing the idea of having the development server >>> >> explicitly set something to indicate a "in development" status, so >>> >> that if that does not exist you can make the assumption that the >>> >> project is live. >>> >>> > This is exactly what the settings.DEBUG flag is for. Use it. Love it. >>> >>> > Jacob >>> >>> > -- >>> > You received this message because you are subscribed to the Google Groups >>> > "Django developers" group. >>> > To post to this group, send email to django-develop...@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> > django-developers+unsubscr...@googlegroups.com. >>> > For more options, visit this group >>> > athttp://groups.google.com/group/django-developers?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To post to this group, send email to django-develop...@googlegroups.com. >> To unsubscribe from this group, send email to >> django-developers+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> >> > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
