fix: 🐛 setting the keys correctly for production NODE_ENV #52
Conversation
This file contains hidden or 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
use the PRIVATE_KEY from environment variable and fix issue with nconf.set not working properly
lessp
approved these changes
Oct 9, 2019
Contributor
lessp
left a comment
lessp
left a comment
There was a problem hiding this comment.
Cool, this looks good to me!
ghost
pushed a commit
that referenced
this pull request
Oct 9, 2019
## [0.31.1](v0.31.0...v0.31.1) (2019-10-09) ### Bug Fixes * 🐛 setting the keys correctly for production NODE_ENV ([#52](#52)) ([cb22cb3](cb22cb3))
|
🎉 This PR is included in version 0.31.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
ghost
added
the
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.
use the PRIVATE_KEY from environment variable and fix issue with nconf.set not working properly