the mentioned "local_config.py.default" is ONLY a template for
copying, its never really used.
wolfram
On 7/25/07, Wolfram Kriesing <[EMAIL PROTECTED]> wrote:
> we are doing the following pretty successfully:
> inside settings.py
> --
>
> import local_config
>
> DEBUG =
we are doing the following pretty successfully:
inside settings.py
--
import local_config
DEBUG = local_config.DEBUG
TEMPLATE_DEBUG = local_config.DEBUG
LOG_LEVEL = local_config.LOG_LEVEL
DATABASE_ENGINE = local_config.DATABASE_ENGINE
DATABASE_NAME =
Thanks for the help.
That's going to save me heaps and heaps of time.
Thanks again.
Goran
On Jul 25, 10:01 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On 7/24/07, gorans <[EMAIL PROTECTED]> wrote:
>
>
>
> > I though that there could be a way to trick Django into reading
> > special
On 7/24/07, gorans <[EMAIL PROTECTED]> wrote:
>
> I though that there could be a way to trick Django into reading
> special development settings for me, something like having a settings
> 'package' import separate settings files:
No need for any special handling - just use the --settings option
One solution is to add an extra import at the bottom of your
settings.py:
try:
from localsettings import *
except ImportError:
pass
Then put localsettings.py in your svn:ignore, and override whatever
settings you need to on a per-installation basis.
On Jul 24, 2007, at 8:41 AM,
5 matches
Mail list logo
