On 25/10/10 19:04, Jumpfroggy wrote:
> - +1 on using "settings.py" and "local_settings.py". The problem with
> keeping local settings files in the VCS is when you have multiple
> servers with different settings. You could store each file as
> local_settings_test_server.py and so on.
We use a proj.settings along the lines of:
from proj.common_settings import *
import imp
imp.load_source('proj_local_settings', '/etc/proj/settings.py')
from proj_local_settings import *
to keep our host-specific settings outside VCS on each host. A range of
more complex schemes are possible, of course.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
