On Sun, 2006-08-06 at 09:41 +0800, limodou wrote:
> When you create a new project, django-admin.py will create a
> SECRET_KEY and saves it in settings.py. Sometimes we are developing an
> open source project, so we'll bring settings.py to public also. And
> also make SECRET_KEY openned. So I think if django-admin.py could
> create a file(maybe .key or key) when creating the project, and change
> the SECRET_KEY to:
>
> SECRET_KEY = file('.key', 'rb').read()
If you want to pull the secret key from a file, just do it like that in
settings.py. That is why settings.py is a Python file.
It's not really worth the hassle doing this by default, since making
settings.py universally safe for distribution would be very hard. That
is something each project distributor needs to decide and manage for
themselves based on circumstances.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
