On Fri, Sep 16, 2011 at 8:54 PM, Tim Chase
wrote:
> Just returning to some Django work after a time away, I (re)started an old
> project in 1.3 and hit an early issue. I'd like to keep my settings.py
> under revision-control that is somewhat publicly accessible,
In addition you can add a local_settings.py.template on repository instead
of local_settings.py, so for developtment you can add some fixed fake values
for testing and edit with production suitable values when needed.
2011/9/17 Donald Stufft
> $ cat settings.py
>
> ….
$ cat settings.py
….
try:
from local_settings import *
except ImportError:
pass
$ cat local_settings.py
….
SECRET_KEY = "blah"
On Friday, September 16, 2011 at 8:54 PM, Tim Chase wrote:
> Just returning to some Django work after a time away, I
> (re)started an old project in 1.3 and
Just returning to some Django work after a time away, I
(re)started an old project in 1.3 and hit an early issue. I'd
like to keep my settings.py under revision-control that is
somewhat publicly accessible, but don't want my SECRET_KEY
exposed. The solution I've opted for is the following
4 matches
Mail list logo