Integrate EnvKey with your Python projects to keep API keys, credentials, and other configuration securely and automatically in sync for developers and servers.
Compatible with Python 2 and 3.
$ pip install envkey
Then at the entry point of your application:
For Django, you should put the above in
ENVKEY in the EnvKey App. Then set
ENVKEY=..., either in a gitignored
.env file in the root of your project (in development) or in an environment variable (on servers).
Now all your EnvKey variables will be available in
The package will throw an error if an
ENVKEY is missing or invalid.
Assume you have
STRIPE_SECRET_KEY set for the
development environment in the EnvKey App. You generate a local development
In your project's gitignored
# .env ENVKEY=GsL8zC74DWchdpvssa9z-nk7humd7hJmAqNoA
stripe.api_key = os.environ['STRIPE_SECRET_KEY']
STRIPE_SECRET_KEY will stay automatically in sync for all the developers on your team.
For a server, generate a server
ENVKEY in the EnvKey App, then set the
ENVKEY as an environment variable instead of putting it in a
Now your servers will stay in sync as well. If you need to rotate your
STRIPE_SECRET_KEY you can do it in a few seconds in the EnvKey App, restart your servers, and you're good to go. All your team's developers and all your servers will have the new value.
This package will not overwrite existing environment variables or additional variables set in a
.env file. This can be convenient for customizing environments that otherwise share the same configuration. You can also use sub-environments in the EnvKey App for this purpose.
This package caches your encrypted config in development so that you can still use it while offline. Your config will still be available (though possibly not up-to-date) the next time you lose your internet connection. If you do have a connection available, envkey will always load the latest config. Your cached encrypted config is stored in
For caching purposes, it's assumed you're in development mode when a
.env file exists in the root of your project.
If you'd like to have more control over how your config is loaded, you can prevent the package from auto-loading on import by setting
ENVKEY_DISABLE_AUTOLOAD=1 either in your
.env file or as an environment variable.
You can then load your config explicitly like this:
import envkey envkey.load(cache_enabled=True, dot_env_enabled=True, dot_env_path=".env")
For even more flexibility, you can just fetch your config as a dict (without setting it on
os.environ) like this:
import envkey import os config = envkey.fetch_env(os.environ['ENVKEY'], cache_enabled=True)
If you look in the
ext directory of this package, you'll find a number of
envkey-fetch binaries for various platforms and architectures. These are output by the envkey-fetch Go library. It contains EnvKey's core cross-platform fetching, decryption, verification, web of trust, redundancy, and caching logic. It is completely open source.
For more on EnvKey in general:
Read the docs.
Read the integration quickstart.
Read the security and cryptography overview.