On Fri, Dec 2, 2011 at 6:54 AM, kenneth gonsalves <law...@thenilgiris.com> wrote: > On Fri, 2011-12-02 at 11:29 +0000, Bjarni Rúnar Einarsson wrote: >> (for example >> as someone recommended earlier, skipping settings.py), you are IMO >> asking for trouble and it is probably a sign that your processes are >> broken. :-) > > you put your passwords and keys under version control? > -- > regards > Kenneth Gonsalves > > -- > 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. > >
Check out https://code.djangoproject.com/wiki/SplitSettings Personally, I use the second example, "Multiple setting files importing from each other". You can put settings common to both development and production in settings.py and keep it in version control, but have a settings_local.py or something that has things like database connection information (including passwords), SECRET_KEY, and whatever else would be secret or different between development/production. Then .gitignore settings_local.py. I also keep a settings_local.py.template in version control that's just a fill-in-the-blank of settings_local.py for quick set up on a new dev machine or production server. -- John P. Kiffmeyer Email/XMPP: j...@thekiffmeyer.org -- 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.
