ruby on rails: heroku: Missing `secret_key_base` for 'production' environment

Question

I added the key into heroku config var, but I'm still getting the error.

Is this the correct way? I ignored secrets.yml as I read from other sources that its not a good idea to push this to the public.

in the heroku config var:

[key] SECRET_KEY_BASE
[value] 3280570382948240938

in secrets.yml

production:
  secret_key_base: <%= ENV["SECRET_KEY_BASE"] %>

What am I still doing wrong?

Furthermore, if I put my secret keys into heroku's config variable, don't other developers get to see this too? So, isn't that still kind of public? I've always wondered this concept.

Cassino

Other developers cannot see your environment variables, since each Heroku app runs on a separate virtual service instance. – July

Answer 1

you can set environment variable with heroku config

first generate secret key with run below command on terminal

rake secret

Now use that key on below command

heroku config:set SECRET_KEY_BASE='put here new generated key'

you can refer this link for more refference

https://devcenter.heroku.com/articles/config-vars

Muscovado

Answer 2

I had the same issue today, but for me the solution was a bit different. I realized that in my local environment, I had been using:

Rails.application.secrets.secret_key_base

but for Heroku, instead use:

Rails.application.secret_key_base

^This worked in my local environment as well. Not sure what the extra .secrets is for.

Hibernaculum

I also had the same issue which this fixed. Rails 6 + following a Scotch Rails API tutorial. – Willable

Answer 3

here is a fool-proof way to set the secret key base with heroku:

heroku config:set SECRET_KEY_BASE=$(rake secret)

you can see it with heroku config:get SECRET_KEY_BASE

and check that rails picks it up with Rails.application.secret_key_base (in heroku run rails console for instance)

Resemble

Answer 4

With heroku it will setup a master.key file for you when the initial deployment is complete, you just need to grab the values from that file. No need to mess with creating extra files in rails 7+ and Heroku sets up the SECRET_KEY_BASE env var for you automatically, just do the following below:

go to config/environments/production.rb

find this line that is commented out (aprox line 20ish) and remove the comment config.require_master_key = true

next go to your console and run this command to get the .gitignored master.key value to populate into the heroku env vars

heroku config:set RAILS_MASTER_KEY=`cat config/master.key`

# yes thats a tilda, make sure it remains a tilda so that the shell command executes

Was not super clear, had to dig through several docs and issue tickets to figure it out, hope it helps

Decrease