"When you install a new django application, you have to add/modify your settings.py module."
I think this is fine as is.
I don't see any reason to change or modify this at all.
What we do, however, is to "subclass" the core settings module.
Our developer-specific and installation-specific files have names like settings_devxy_linux2
and settings_checkout_win32
, etc.
Each of these files starts with from settings import *
to import the core settings and extend those core settings with overrides for a specific installation and platform.
It doesn't require any real work. It does, however, mean that we do most things with django-admin.py
because our settings aren't called settings
.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…