-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Devise.secret_key was not set #170
Comments
Hmm, I’m running it with |
It is set on the production environment on heroku |
I dont have this problem when I run it locally. |
i'm not hitting this when i run locally after upgrading to Yosemite. Ill investigate. |
So, I found that the environment sometimes wasn't being . .env.development
export DEVISE_SECRET_KEY
export RAILS_SECRET_KEY then all my stuff worked again. However, this was only happening when I had a newer version of stuff than was locked in the Gemfile.lock - did you run into this error after a |
I have this issue as well, I have made a pull request to fix the issue. |
Also just as a note, we are not all running OSX and we need to make sure the app works without pow etc. |
Whenever I try to run the app (ex. with pow) I get this error:
RuntimeError: Devise.secret_key was not set. Please add the following to your Devise initializer:
config.secret_key = '-----'
Please ensure you restarted your application after installing Devise or setting the key.
I know we set the key in devise.rb, so I'm surprised to get this error. I get the same error when I change the key environment variable to the new key given in the error message and restart the app.
The text was updated successfully, but these errors were encountered: