From 5e62e771bf14f58dd1622d2e3631309caa201349 Mon Sep 17 00:00:00 2001 From: Kelly Rauchenberger Date: Sat, 16 Sep 2017 18:46:55 -0400 Subject: Initial commit --- test/dummy/config/secrets.yml | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 test/dummy/config/secrets.yml (limited to 'test/dummy/config/secrets.yml') diff --git a/test/dummy/config/secrets.yml b/test/dummy/config/secrets.yml new file mode 100644 index 0000000..0a556f8 --- /dev/null +++ b/test/dummy/config/secrets.yml @@ -0,0 +1,32 @@ +# Be sure to restart your server when you modify this file. + +# Your secret key is used for verifying the integrity of signed cookies. +# If you change this key, all old signed cookies will become invalid! + +# Make sure the secret is at least 30 characters and all random, +# no regular words or you'll be exposed to dictionary attacks. +# You can use `rails secret` to generate a secure secret key. + +# Make sure the secrets in this file are kept private +# if you're sharing your code publicly. + +# Shared secrets are available across all environments. + +# shared: +# api_key: a1B2c3D4e5F6 + +# Environmental secrets are only available for that specific environment. + +development: + secret_key_base: d94a7920fc6bda3f336cd79bd15d3d75aa6ebab77fc6f48649ffda7b42d7869a73bc0f1f11cb6f4a5db138a9c162602d31e99cc90fb7658aaf38c495ff44861f + +test: + secret_key_base: 0ac56d59b80aab985c4e789a8c4c293c585ad31a5abe62acd4eda31e4f87211b1f86652e75a637485d052932b01a1b502ac0620052b0a68bbf9c01e85b721793 + +# Do not keep production secrets in the unencrypted secrets file. +# Instead, either read values from the environment. +# Or, use `bin/rails secrets:setup` to configure encrypted secrets +# and move the `production:` environment over there. + +production: + secret_key_base: <%= ENV["SECRET_KEY_BASE"] %> -- cgit 1.4.1