James Bennett wrote:
> On 11/1/07, Carl Karsten <[EMAIL PROTECTED]> wrote:
>> Given that some settings.py files get shared/posted/uploaded to code.google,
>> etc. it seems this should not be in there by default:
>>
>> # Make this unique, and don't share it with anybody.
>> SECRET_KEY = 'foo!'
>
> By the same token, then, the database settings shouldn't be in the
> settings file ;)
>
> (same goes for things like API keys, passwords for externally-accessed
> services...)
>
Yeah, I sense an enhancement...
When you run django-admin.py startproject mysite a settings.py gets created
with
lots of stuff. I am wondering if these should be pulled out:
SECRET_KEY = 'foo!'
DATABASE_ENGINE = ''
DATABASE_NAME = ''
DATABASE_USER = ''
DATABASE_PASSWORD = ''
DATABASE_HOST = ''
DATABASE_PORT = ''
and put in local_settings.py or something along these lines.
# this will attempt to load a file called local_settings.py
# which will override the information here.
try:
from local_settings import *
except ImportError:
pass
I am even thinking it might be a good idea to store them in a
/home/user/.mysite/local_settings.py
or something that uses os.path.expanduser('~')
So that it is kept separate from the stuff that is not 'private.'
I can't really see a need to keep it version controlled, and hardly a point in
other developers working on a project needing it to get automatically updated.
(I can imagine a rare case, but I think the normal danger trump that
convenience.) I do pull a copy to a fresh box for testing, and it will be a
slight bother to have to manually move those settings around. but 1/2 the time
I end up setting up a test DB/user anyway. I sure don't need to keep copies of
passwords archived.
So before I go hacking up a patch, any comments ?
Carl K
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
