On Thu, Sep 26, 2013 at 2:21 PM, Andres Osinski <andres.osin...@gmail.com> wrote: > Honestly, I find the idea of *not* using a settings file to be inconvenient, > and the notion of using environment variables for doing anything aside from > pointing to a settings file to be pretty disgusting.
+1 The idea that before you start working on a project you need to infer and set the 50 or so environment variables required is anathema to me. The most important concern is that these settings are not part of your code, they are part of your configuration. Consistency of configuration is one of the most important things in DevOps, and so IMHO the most important thing in your project is tracking and managing the changes in your configuration. To me, that means one thing. Configuration files live in VCS repositories - this is the only way to track changes to your configuration, to validate that there are no unexpected changes to the file. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
