Did you read my post? > I don't like having to check for specific things > like to see if I'm in live or development mode in my settings
I'm talking about having 2 sets of settings, and differentiating them without having to use stuff like ``import os`` or web server specific things to discern between the two settings files. Telling your application to use "Live" settings should not have to be coupled to your deployment strategy. Did you look at the link I posted. The blog post offers a terrible solution to a problem that shouldn't exist. On Sep 23, 3:25 pm, 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 at http://groups.google.com/group/django-developers?hl=en.
