title: Rails 4.1 pushing secrets to heroku
body: <p>Rails 4.1.0.beta1 and Devise.</p>
  
  <p>I'm trying to remove all of my keys from version control and I've upgraded to Rails 4.1 to give this new secrets.yml a shot</p>
  
  <p>Trying to push Devise's <code>config.secret_key</code> to heroku but it's failing after assets:precompile</p>
  
  <pre><code>Preparing app for Rails asset pipeline
         Running: rake assets:precompile
         rake aborted!
         Devise.secret_key was not set. Please add the following to your Devise initializer:
         config.secret_key = 'EXAMPLE_KEY_HERE'
         Please ensure you restarted your application after installing Devise or setting the key.
  </code></pre>
  
  <p>Here are my changes, the old code I'll leave in comments.  (it works)</p>
  
  <p><code>devise.rb</code></p>
  
  <pre><code>  # config.secret_key = 'THIS_IS_A_FAKE_KEY' #&lt;---this_is_commented_out
    config.secret_key = Rails.application.secrets.devise_secret_key
  </code></pre>
  
  <p><code>secrets.yml</code></p>
  
  <pre><code>production:
    devise_secret_key: 'THIS_IS_A_FAKE_KEY'
  </code></pre>
  
  <p>then ran <code>heroku labs:enable user-env-compile -a myapp</code>  (not sure if that's necessary)</p>
  
  <p>and then when I push to my forked heroku envionment <code>git push forked master</code> I get the above error.</p>
  
  <p>I also noticed some discussion on this in this Devise repo so I figured I'd update my gem alongside the source repo, no difference.  Here's part of that discussion (<a href="https://github.com/plataformatec/devise/pull/2835">here</a>).</p>