removed devise secret

config/application-example.yml

@@ -2,6 +2,12 @@ defaults: &defaults
   app_name: .EE Registry
   zonefile_export_dir: 'export/zonefiles'
 
+  # You can use `rake secret` to generate a secure secret key.
+  # Your secret key is used for verifying the integrity of signed cookies.
+  # If you change this key, all old signed cookies will become invalid!
+  secret_key_base: please-change-it-you-can-generate-it-with-rake-secret
+  devise_secret: please-change-it-you-can-generate-it-with-rake-secret
+
 development:
   <<: *defaults
 

config/deploy.rb

@@ -36,9 +36,8 @@ end
 # Manually create these paths in shared/ (eg: shared/config/database.yml) in your server.
 # They will be linked in the 'deploy:link_shared_paths' step.
 set :shared_paths, [
-  'config/initializers/devise_secret.rb',
+  'config/application.yml',
   'config/database.yml',
-  'config/secrets.yml',
   'log',
   'public/system',
   'export/zonefiles'

config/initializers/devise.rb

@@ -4,9 +4,8 @@ Devise.setup do |config|
   # The secret key used by Devise. Devise uses this key to generate
   # random tokens. Changing this key will render invalid all existing
   # confirmation, reset password and unlock tokens in the database.
-  # config.secret_key = 'd4827f0d88c93db5c68eb43d7f86dc141ea7c44ca8f' \
-  # '044773265a2aa8786122c4364271960a10a956701c3c5fd4509e9c9780886200a3b772e6185271001987'
-
+  config.secret_key = APP_CONFIG['devise_secret']
+  
   # ==> Mailer Configuration
   # Configure the e-mail address which will be shown in Devise::Mailer,
   # note that it will be overwritten if you use your own mailer class

config/initializers/devise_secret_example.rb.txt

@@ -1,5 +0,0 @@
-# Please generate production secret with 'rake secret' command
-# example secret: 'c831d559c77de1e6544ed4954d5752c294d2390036e45962dc0d44942f20db795ab7b0485b34faf237183660348e3192344404f52df7dee23d8031521d550f89'
-Devise.setup do |config|
-  config.secret_key = 'please-change'
-end