Expand explanation of how to set secrets.yml. #14654
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
|
👍 make sense to me.. |
rafaelfranca
added a commit
that referenced
this pull request
Apr 9, 2014
Expand explanation of how to set secrets.yml.
rafaelfranca
added a commit
that referenced
this pull request
Apr 9, 2014
Expand explanation of how to set secrets.yml.
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.
The guide for upgrading to Rails 4.1.0 suggests copying the existing secret_key_base from the secret_token.rb initializer to secrets.yml under the production section. This is considered insecure by default in Rails 4.1.0, which generates a secrets.yml containing <%= ENV["SECRET_KEY_BASE"] %> for production mode:
This expanded explanation shows both ways of setting secret_key for production mode.