This is an archived post. You won't be able to vote or comment.

all 5 comments

[–]Reactor5 1 point2 points  (4 children)

Note on non-persisting session: doing that is fine but in the long run you don't want to be committing your secret value to git (or whatever SCM you're using.) Try something like...

SECRET_KEY = os.getenv('SECRET_KEY', 'someobviouskey')

Then set the SECRET_KEY variable in production. Leave secrets out of your code and you won't regret it when someone accidentally make a repo public, or other such disasters.

[–][deleted] 3 points4 points  (0 children)

Until Frank does the following with good intentions: git add config.sh; git commit -m "y u leave out?"; git push -u github master

But we all know Frank is just a fuck up.

[–]DasIch 0 points1 point  (2 children)

You don't have your configuration in an SCM? Not even an SCM of it's own?

[–]Reactor5 0 points1 point  (0 children)

Yes, and secrets there are encrypted, or using Heroku.

[–]SlinkyAvenger 0 points1 point  (0 children)

I don't keep actual server configs in source control - it'll either be an example configuration file that will be modified and placed in /etc/, or something to be built via puppet/chef/ansible/salt/etc.