Defect #19185

Update Install/Upgrade guide for 3.x version and get gid of DEPRECATION WARNING: You didn't set config.secret_key_base

Added by Pavel Potcheptsov about 3 years ago. Updated almost 3 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:Documentation
Target version:3.0.2
Resolution: Affected version:3.0.0

Description

Need to add section for 3.x install and upgrade to 3.x where change such text

Run the following command from your new Redmine root directory:

bundle exec rake generate_secret_token

This will generate a file (config/initializers/secret_token.rb) with a random secret used to secure session data.

to something like:
- follow official guide
- or just create secrets.yml file with such content:
production:
  secret_key_base:

- run rake secret and copy/paste output after secret_key_base:
Otherwise you'll get DEPRECATION WARNING: You didn't set config.secret_key_base in your production.log


Related issues

Related to Redmine - Patch #20292: Ignore Secrets.yml file Closed

Associated revisions

Revision 14217
Added by Jean-Philippe Lang about 3 years ago

Upgrade guide for 3.x version and get gid of DEPRECATION WARNING: You didn't set config.secret_key_base (#19185).

History

#1 Updated by Toshi MARUYAMA about 3 years ago

  • Target version set to 3.0.2

#2 Updated by Toshi MARUYAMA about 3 years ago

  • Subject changed from Update Wiki Install/Upgrade guide for 3.x version and get gid of DEPRECATION WARNING: You didn't set config.secret_key_base to Update Install/Upgrade guide for 3.x version and get gid of DEPRECATION WARNING: You didn't set config.secret_key_base

Not only wiki but also source:tags/3.0.1/doc .

#3 Updated by Olivier Houdas about 3 years ago

Note: secrets.yml should be in /config (whereas secret_token.rb was in /config/initializers)

#4 Updated by Jean-Philippe Lang about 3 years ago

  • Status changed from New to Closed
  • Assignee set to Jean-Philippe Lang

rake generate_secret_token was changed to generate the config.secret_key_base, it's fine for new installs. The problem occurs when upgrading from 2.x. Additional information is added the docs in r14217.
Thanks for pointing this out.

#6 Updated by Toshi MARUYAMA almost 3 years ago

Also available in: Atom PDF