What about importing skeleton.py at the bottom of your settings file then?
On 6/18/07, Jared Kuolt <[EMAIL PROTECTED]> wrote:
>
> The skeleton exists to overwrite the settings.py that is generated so
> I don't have to modify things like TIME_ZONE, MEDIA_URL, etc, as well
> as have my extra bit
The skeleton exists to overwrite the settings.py that is generated so
I don't have to modify things like TIME_ZONE, MEDIA_URL, etc, as well
as have my extra bits that I like:
if getpass.getuser() == 'jared':
PROJECT_DIR = '/Users/jared/Desktop/project/'
DATABASE_ENGINE = 'mysql'
DATAB
On 6/18/07, Jared Kuolt <[EMAIL PROTECTED]> wrote:
>
> I have a common set of extra bits that I put in my settings.py files
> and re-input them each time I create a project. I would like to have a
> directory like ~/.django_skeletons/project that houses my customized
> settings.py (and perhaps oth
I have a common set of extra bits that I put in my settings.py files
and re-input them each time I create a project. I would like to have a
directory like ~/.django_skeletons/project that houses my customized
settings.py (and perhaps others).
It seems to me this would be a fairly simple undertaki
