Project

General

Profile

Actions
Copy link

Refactor #14022

closed

secret_key_base should be configured

Added by Dominic Cleal almost 9 years ago. Updated almost 9 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Rails
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Rails 4.1 adds a secrets.yml file that should be configured with a secret_key_base per environment. This replaces the secret token initialiser. Deprecation warnings are currently being issued by Rails:

DEPRECATION WARNING: You didn't set `secret_key_base`. Read the upgrade documentation to learn more about this new config option. (called from validate_secret_key_config!

http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#config-secrets-yml has more info.

This will need some updates to packaging too, since we have scripts to generate the tokens and link the files into the right place post-installation.

Related issues 2 (0 open — 2 closed)

Related to Foreman - Feature #7230: Upgrade Ruby on Rails to 4.1ClosedDaniel Lobato Garcia08/22/2014Actions
Is duplicate of Foreman - Refactor #7570: set secret_key_base for rails 6.0 upgradeClosedTomer BriskerActions
Actions
Copy link
 #1

Updated by Dominic Cleal almost 9 years ago

Actions
Copy link
 #2

Updated by Brandon Weeks almost 9 years ago

  • Blocks Refactor #7570: set secret_key_base for rails 6.0 upgrade added
Actions
Copy link
 #3

Updated by Dominic Cleal almost 9 years ago

  • Blocks deleted (Refactor #7570: set secret_key_base for rails 6.0 upgrade)
Actions
Copy link
 #4

Updated by Dominic Cleal almost 9 years ago

  • Is duplicate of Refactor #7570: set secret_key_base for rails 6.0 upgrade added
Actions
Copy link
 #5

Updated by Dominic Cleal almost 9 years ago

  • Status changed from New to Duplicate
Actions
Copy link

Also available in: Atom PDF