Kenneth Gonsalves: > > anyway, putting settings.py under version control is tantamount to > > suicide, so all you need to do is change your settings.py on each > > installation I'm sorry I don't understand this. Suppose you get a bug report having to do with version 3.2.1 (your development version is 4.3.2). How do you reproduce the environment? Do you know your settings.py will never change?
On Sep 5, 9:25 am, brad <[EMAIL PROTECTED]> wrote: > I've also run into the problem of > keeping my settings.py under version control, so I just created > multiple settings files for the various servers on which my apps would > run, so I've got: > > settings.py > settings_server1.py > settings_server2.py > settings_dev.py > > I know this violates DRY to some degree, but it's fairly easy to just > copy the appropriate settings file over to settings.py whenever I > deploy the app. I have an installation-from-repo routine that, in part, looks up the hostname and generates the appropriate settings.py (and some other stuff) and puts it where it should go. Obviously the installation routine costs me a certain effort of coding, debugging, etc., so it may not be worth it for some projects, but at least it solves that problem. Jim --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
