Added ability to store keys in the environment variables #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks good, thanks! ⭐ ⭐ |
danielberkompas
added a commit
that referenced
this pull request
Dec 16, 2015
Added ability to store keys in the environment variables
|
@mspanc I finally got around to merging all your PRs and released a new version of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is a good practice to store keys, secret tokens in the environment variables. Then they are never committed into repository, and this is de facto standard in environments such as Heroku.
This PR adds possibility to define that keys are stored in the environment using
{:system, something}syntax that is often used by the Phoenix Framework.