On 9/25/06, Scott McCracken <[EMAIL PROTECTED]> wrote:
>
> In continuing to diagnose this problem I have re-read the
> DJANGO_SETTINGS documentation. Under the section for Default Settings
> it says:
>
> "A Django settings file doesn't have to define any settings if it
> doesn't need to. Each setting has a sensible default value. These
> defaults live in the file django/conf/global_settings.py.
>
> Here's the algorithm Django uses in compiling settings:
> * Load settings from global_settings.py.
> * Load settings from the specified settings file, overriding
> the global settings as necessary."
>
> Is it possible to adjust that algorithm to
>
> * first load settings from the global_settings.py
> * second load settings from a common project settings.py
> * third load settings from a specific project's settings.py
>
> In other words, is there a way to have another level of settings in
> between global and project-level without modifying the django_src.
Sure, the settings file is just python code so at the top of your
settings.py do something like:
from myproject.commonsettings import *
Of course, this assumes the file myproject/commonsettings.py
--
----
Waylan Limberg
[EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
