---------- Forwarded message ----------
From: Philippe M. Chiasson <go...@ectoplasm.org>
Date: Wed, Sep 23, 2009 at 9:45 PM
Subject: Re: settings.py
To: Eric Henry <ehe...@gmail.com
On 09-09-23 21:34 , Eric Henry wrote:
> Alright, I'll get on that.
Also, while at it, I'd like to see if something is possible.
Breaking settings.py in 2-3 pieces.
First, a settings.py that contains all app-specific settings (i.e. that
have nothing to do with where it's installed/deployed), things like
plugins to load, etc
Second, a set of production/staging .pys that just contains what's
specific to the installation mode (i.e. paths, debug settings, etc) that
pulls the rest of the settings from the main settings.py
Third, some shared logic somewhere that looks for some sort of local
override settings file, something like settings-local.py in the project
directory, and if present, loads it last, allowing it to
redefine/override pretty much anything it wants.
Let me know if any of this doesn't make sense.