Switching to new secrets format #710
Merged
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
| # run 'rake secret' to generate your own | ||
|
|
||
| production: | ||
| secret_key_base: <%= ENV["SECRET_KEY_BASE"] %> |
There was a problem hiding this comment.
I'll fix the missing line break shortly.
There was a problem hiding this comment.
Where is this set? How is it pushed to Heroku? Please check application.yml (or the example one that's in github, anyway) and modify if necessary.
There was a problem hiding this comment.
Ah, I meant to have it with the same name as the old one, so it would be no change in production/Heroku. Will fix.
1 similar comment
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.
I found that rake was failing in my dev environment. The cause seems to be http://guides.rubyonrails.org/upgrading_ruby_on_rails.html#config-secrets-yml
Is this an issue for anyone else?