Quick tip: Adding Variables to env in a Virtualenv (for development purpose)

Posted by Luis Alberto Santana on Thursday, Jul 16, 2015

If you're working with third party APIs, you might find code like YOUR_SECRET_KEY="some secret api key" in your source code, this is a bad practices for a lot of reasons (security, source code sharing, etc). Instead, the recommended way to manage this kind of situation is to add the value as a enviroment variable, and read it in your code with something like this:

import os

So, how do you avoid to add the variable to the enviroment each time you do some coding? If you're working with virtualenv you simply add it in the env/bin/activate script:

YOUR_SECRET_KEY="some secret api key"

Comments !