Rails 5 Generate Secret_key_base

by
Rails 5 Generate Secret_key_base Average ratng: 4,8/5 1168 votes

Join GitHub today

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

/keytool-generate-public-key-from-certificate.html.

The release of Rails 5.1 added another file named secrets.yml.enc to allow for encrypting your secret credentials, but this caused some confusion. The combination of config/secrets.yml, config/secrets.yml.enc, and SECRETKEYBASE made it so it wasn’t clear where secrets should be stored and what the relevance of SECRETKEYBASE was 2. Dec 22, 2017 Rails 5.1 introduced Encrypted Secrets to help simplify the management of your application secrets (things such as service credentials and the secretkeybase). This article details the feature and its usage. Why Encrypted Secrets? Since Rails 4.1, the framework has given you the ability to centrally store secrets in the config/secrets.yml file. The glaring shortcoming of. Secretkeybase: <%= ENV'
Sign up 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:

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:

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

commented May 19, 2014

Rails generate model

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.

Rails Generate Model

closed this May 19, 2014

Rails Generate Secret_key_base

Rails 5 generate secret_key_base pdf

Rails 5 Generate Secret_key_base Download

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment