Rails Generate Secret_key_base For Production

May 21, 2019 The master key file generated by Rails (config/master.key) as explained above. The Rails production database password that we will pass in the DATABASEPASSWORD environment variable. Aug 02, 2019 app error: Missing `secretkeybase` for 'production' environment, set this value in `config/secrets.yml` (RuntimeError) - secretkeybase. $ RAILSENV=production rake secret: This will give a large string with letters and numbers, this is what you need, so copy that (we will refer to that code as GENERATEDCODE). Devise.secretkey was not set. Please add the following to your Devise initializer. Rails generate devise MODEL. 'SECRETKEYBASE' if Rails.env.production? Devise.setup do config # The e-mail address that mail will appear to be sent from # If absent, mail is sent from 'please-change-me-at-config-initializers-devise@example.com'. Secretkeybase: 492f. Production: secretkeybase: <%= ENV'

Join GitHub today

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments

commented May 19, 2014

I have recently deployed an app and got internal server error because of missing production secret_key_base. After hours of testing, I managed to solve this problem with two methods:

Method 1:

I generated a new secret_key with rake secret and replaced it with <%= ENV['SECRET_KEY_BASE'] %> in secrets.yml. Deployed the app again and this time it worked. But I think that this method is wrong.

Method 2:

This generator is very easy to use. With it you can generate keys/beta keys for Diablo III. Diablo III Key Generator is developed with “FGM Generator Engine” which gives auto updater, anti-ban function, protection for privacy policy of Diablo 3 game, script undetectable by Diablo 3 game system. Diablo 3 online key generator. Diablo III Gey Generator Informations:This Diablo 3 Key Generator was developed by “HackCrackInjector” team.

I generated a new secret_key with rake secret and added it to environments/production.rb like config.secret_key_base = 'd1f4810e662acf46a33960e3aa5bd0************************, without changing secrets.yml (default is production: <%= ENV['SECRET_KEY_BASE'] %>). Deployed the app again and it works fine.

My questions:

Which method is the best?
If the 2nd method is correct, why rails does not generate a secret_key_base in production.rb by default?
Is there any other method to do that?

commented May 19, 2014

As the name implies, secret_key_base should be a secret. That's why we don't generate a secret for production in config/secrets.yml. You see that it's reading from an environment variable so you can easily set your secret on your production server, without changing the file:

If you want / need to have your secret under version control, you should definitely stick with Method 1. That's because Method 2 just avoids the config/secrets.yml mechanism all together.

Please note that we don't use GitHub for support questions. Read our contribution guidelines and please use the rails-talk mailing list for further questions.