Contents

# 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: 75b70e890639a171b634affb1d3f58a93142c0dd9e9e4e2631b008435ed593d1d8dc689288ca3d7b1b5e58ea091b8f992fddbeb8238da7fe03db0f02e39c242f

test:
  secret_key_base: 29fd6d44ee68c2b8b190449faf9ba6e9b045445d0cebf32abb28936bd4af877f1ffa0cda57c4741bc498a8b0c86bd7b46803b43b5d96a076f32d6d99f54e34f0

# 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"] %>

Version data entries

4 entries across 4 versions & 1 rubygems

Version	Path
workarea-product_badges-1.4.1	test/dummy/config/secrets.yml
workarea-product_badges-1.4.0	test/dummy/config/secrets.yml
workarea-product_badges-1.3.3	test/dummy/config/secrets.yml
workarea-product_badges-1.3.2	test/dummy/config/secrets.yml