settings.py

[Eric Henry]

Has anyone already made a fix to settings.py? Right now it has
absolute paths to d:/users/davida/, and I would like to convert it to
use relative paths, but if someone has already done it, I don't want
to do it again...

Eric

[David Ascher]

gozer must have done something to deal with that, cause i'm quite sure
the preview site isn't using that directory structure.

gozer?

[Eric Henry]

Alright, I'll get on that.

Eric

On Wed, Sep 23, 2009 at 9:24 PM, Philippe M. Chiasson <go...@ectoplasm.org> wrote:

Yes, that would be awesome! Right now, I've simply added some more paths
into it for production, and left the davida stuff in there.

Needs cleaning up!

--
Philippe M. Chiasson     GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5
http://gozer.ectoplasm.org/       m/gozer\@(apache|cpan|ectoplasm)\.org/

[Eric Henry]

Eric

---------- 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.