On Wed, Dec 12, 2012 at 9:32 PM, Chris Cogdon <ch...@cogdon.org> wrote: > The BIG advantage here is that you're not checking anything into the SCM > that must remain secret, or must change (or very likely to change) between > installations, but all other settings are source controlled.
The big disadvantage is that the configuration of your production website instances are not in a VCS, you cannot track or merge changes to them or their ancestors, and if a box goes kabluie, you can't instantly re-create it. Configuration is code, code lives in a VCS. (Our configuration files live in a separate repository to the project or app code, and are finangled into place based upon the hostname) Cheers Tom -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
