Missing `secret_key_base` for 'test' environment, set this value in `config/secrets.yml`

Startouf · July 16, 2016, 5:50pm

When building the tests on CircleCI, all my tests fail with an error related to not finding the secret_key_base (see below)

I have also found this similar topic on circleCI, but the guy actually didn’t have problems with the secret_key_base, just with other environment variables.

My config/secrets.yml is not committed in my repository, and I have deployment scripts that had generated the secrets on my production infrastructure. I don’t know how this should be handled on CircleCI, I’m actually quite surprised this is not handled by default by circle (eg generating a random secret), or that nobody had the same problem.

I am using Ruby 2.3 and Rails 5. Maybe this is coming from those versions ?

The value of this variable doesn’t really matter I guess since it’s just for testing, so what should I do about it ?

*DEPRECATION WARNING: You didn’t set secret_key_base. Read the upgrade documentation to learn more about this new config option. (called from load at /home/ubuntu/MyJobGlasses/vendor/bundle/ruby/2.3.0/bin/rspec:22)

An error occurred in an after hook
NoMethodError: undefined method original_path_set' for nil:NilClass occurred at /home/ubuntu/MyJobGlasses/vendor/bundle/ruby/2.3.0/gems/rspec-rails-3.1.0/lib/rspec/rails/view_rendering.rb:96:in block (2 levels) in module:ViewRendering’

FelicianoTech · July 17, 2016, 9:16pm

You can just set it to whatever you want. For example:

github.com

circleci/docker-hello-google/blob/master/circle.yml#L27


  - sudo /opt/google-cloud-sdk/bin/gcloud --quiet config set container/cluster $CLUSTER_NAME
  # Reading the zone from the env var is not working so we set it here
  - sudo /opt/google-cloud-sdk/bin/gcloud config set compute/zone ${CLOUDSDK_COMPUTE_ZONE}
  - sudo /opt/google-cloud-sdk/bin/gcloud --quiet container clusters get-credentials $CLUSTER_NAME
  - docker build -t us.gcr.io/${PROJECT_NAME}/hello:$CIRCLE_SHA1 .
  # Using a separate tag command until Docker 1.10 is available on CircleCI, then we can use two tags in the build command above
  - docker tag us.gcr.io/${PROJECT_NAME}/hello:$CIRCLE_SHA1 us.gcr.io/${PROJECT_NAME}/hello:latest


test:
post:
  - docker run -d -p 3000:3000 -e "SECRET_KEY_BASE=abcd1234" us.gcr.io/${PROJECT_NAME}/hello:$CIRCLE_SHA1; sleep 10
  - curl --retry 10 --retry-delay 5 -v http://localhost:3000


deployment:
prod:
  branch: master
  commands:
    - ./deploy.sh

jeremywadsack · August 15, 2016, 8:32pm

Setting an environment variable doesn’t work for me. If you have checked in a config/secret.yml file that included something to read it from the environment that might (like the the default Rails configuration for production). As with the OP we don’t have any config/secrets.yml checked in.

I ended up having to just add a command in my circle.yml to make this work:

dependencies:
  pre:
    - 'echo -e "test:\n  secret_key_base: abcd1234" > config/secrets.yml'

I am also surprised that Circle doesn’t do this by default.

Startouf · August 17, 2016, 8:38am

I chose to add the token in my test environment file. I guess it could be hardcoded, I just decided to generate a random one :

In config/environments/test.rb

# Generate a random secret token
config.secret_token = SecureRandom.hex(64)

Topic		Replies	Views
How can I set secrets.yml for test environment for CircleCI? Build Environment rails	4	13038	June 18, 2018
Can't access env variables from my yml file Build Environment	9	19926	June 18, 2018
Stubbing Rails Secrets into Build Build Environment rails , ruby	14	3090	January 28, 2019
Strange bug on upgrading from Rails 5.1 Feedback & Bug Reports rails	0	2097	December 2, 2019
Could you tell me how to set Environment Variables? Build Environment android	9	20334	June 18, 2018

Missing `secret_key_base` for 'test' environment, set this value in `config/secrets.yml`

Related topics