On 11/1/07, Carl Karsten <[EMAIL PROTECTED]> wrote: > > So before I go hacking up a patch, any comments ? > > Carl K
Don't put your production settings into version control if it's publicly accessible? Personally speaking, if my project's codebase is going to be publicly accessible, I either only ever put development settings into its settings.py (which will usually only be a SQLite database in the project's directory and a dummy SECRET_KEY anyway) for convenience if users just want to try it out quickly, or don't put settings.py into version control at all, only providing a template for it which users would have to copy and customise. Jonathan. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
