6

There doesn't seem to be a configuration option for the secrets.yml check even if I am running Rails as a JSON API

Puma caught this error:

Missing secret_token and secret_key_base for 'production' environment, set these values in config/secrets.yml (RuntimeError)

Any clue what to do? I suppose I can generate a dummy secret_key_base and move on

shivam
  • 16,048
  • 3
  • 56
  • 71
Edward
  • 141
  • 5
  • 18
  • are you sure the `secrets.yml` file is present in your production environment? [This SO suggests git might have ignored it](http://stackoverflow.com/a/23206010/3035830). – shivam Nov 25 '15 at 05:29
  • Okay - to be clear. I don't want to use the secrets.yml - this is a JSON api server – Edward Nov 25 '15 at 07:30

1 Answers1

0

As of 8 March 2022

According to this issue the Rails GitHub project, there is supposed to be a way to disable it but it still isn't working.

This comment mentions how they're supposed to be disabled but that is currently not working.

config.require_master_key = false
config.read_encrypted_secrets = false

As far as I could find, your only option is to provide dummy values at the moment.

Omar Bahareth
  • 875
  • 6
  • 22