[shacker]
>> Another approach to this problem:
>>
>> settings.py IS in version control and includes settings
>> that are universal to all environments (local dev, staging,
>> production), but has dummy info or empty strings for
>> passwords or paths or other information that vary between
>> environments.
> this is a better approach - much more professional (I *did* say I
> am an amateur;-))
A technique I use, having picked it up from Jacob Kaplan Moss, IIRC, is
to keep settings.py under source control but have it include as its last
statement
from local_settings import *
The local_settings.py file is then maintained outside source control on
each target platform. This works very nicely, and allows you to maintain
common settings without having to edit a file that's under code control
to vary settings between platforms.
regards
Steve
--
DjangoCon US 2010 September 7-9 http://djangocon.us/
--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment