CA-Hackathon-Term2/config/secrets.yml
2017-10-19 15:00:34 +11: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: e656ffb2c7f04755ca0001f2b6e11e78514a89b02de6dd6625d2f15639795c41fb23ae470ecaa9e191e01e01c0a94d3517959750793248fd9fa06a3a88e6d5a3
test:
secret_key_base: f01c20bd64c1c631a40271241d44f77e7fdc3c9294a7b522d9509a141e603382c855706c1593d42ea0a9346a35f25931f18c19fc43e9a9ed18864aadaf0dae13
# 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"] %>