vereto-api/config/secrets.yml
2018-02-16 09:12:51 +00:00

32 lines
1.2 KiB
YAML

# 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: 803a8912d7333270ff928870f440d76f3ccec3804ada4f27f52ed4af307c0dd4c5cbaacbda95d5433aa9827ae0b5c7d70b8f6b7121c7111ab58e564b1eae693a
test:
secret_key_base: 7fa5a5c6e17acd1d7f3ac98d8a52a5bec245e729a04ec49af72eca8b5b319a93a0aa3382b88064205608843a23256e8e161bbbe57c270003663d088f557093e1
# 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"] %>