设计令牌auth错误:dease.secret_key未设置

Question

我当前正在使用设计的令牌auth（https://github.com/lynndylanhurley/devise_token_auth）gem，并在开发方面运作良好。但是，在我的生产环境中，当我运行rake db:migrate时，我会收到以下错误：

rake aborted!
Devise.secret_key was not set. Please add the following to your Devise initializer:
  config.secret_key = 'my secret key'
Please ensure you restarted your application after installing Devise or setting the key.
/Users/karimbutt/.rvm/gems/ruby-2.1.2/gems/devise-3.4.1/lib/devise/rails/routes.rb:480:in `raise_no_secret_key'
/Users/karimbutt/.rvm/gems/ruby-2.1.2/gems/devise-3.4.1/lib/devise/rails/routes.rb:209:in `devise_for'
/Users/karimbutt/.rvm/gems/ruby-2.1.2/gems/devise_token_auth-0.1.31/lib/devise_token_auth/rails/routes.rb:25:in `mount_devise_token_auth_for'
/Users/karimbutt/Development/projects/haubby/backend/config/routes.rb:3:in `block in <top (required)>'
/Users/karimbutt/.rvm/gems/ruby-2.1.2/gems/actionpack-4.2.0/lib/action_dispatch/routing/route_set.rb:423:in `instance_exec'
/Users/karimbutt/.rvm/gems/ruby-2.1.2/gems/actionpack-4.2.0/lib/action_dispatch/routing/route_set.rb:423:in `eval_block'
/Users/karimbutt/.rvm/gems/ruby-2.1.2/gems/actionpack-4.2.0/lib/action_dispatch/routing/route_set.rb:401:in `draw'
/Users/karimbutt/Development/projects/haubby/backend/config/routes.rb:1:in `<top (required)>'

当我添加秘密键时，正如错误消息所建议的那样，我会收到以下错误：

rake aborted!
NoMethodError: undefined method `secret_key=' for DeviseTokenAuth:Module
/Users/karimbutt/Development/projects/haubby/backend/config/initializers/devise_token_auth.rb:12:in `block in <top (required)>'
/Users/karimbutt/.rvm/gems/ruby-2.1.2/gems/devise_token_auth-0.1.31/lib/devise_token_auth/engine.rb:23:in `setup'
/Users/karimbutt/Development/projects/haubby/backend/config/initializers/devise_token_auth.rb:1:in `<top (required)>'

我尝试了以下内容 - 重新安装宝石 - 设置检查以查看rails.env =="生产"在设计配置文件中 - 更新的宝石 - 使用发电机重新安装设计 - 放下桌子，并用发电机创建的新迁移

流动

这是我的initializers/devise_auth.rb文件，当我要求键输入密钥时：

DeviseTokenAuth.setup do |config|
  # By default the authorization headers will change after each request. The
  # client is responsible for keeping track of the changing tokens. Change
  # this to false to prevent the Authorization header from changing after
  # each request.
  #config.change_headers_on_each_request = true
  # By default, users will need to re-authenticate after 2 weeks. This setting
  # determines how long tokens will remain valid after they are issued.
  #config.token_lifespan = 2.weeks
  config.secret_key = 'my secret key'
  # Sometimes it's necessary to make several requests to the API at the same
  # time. In this case, each request in the batch will need to share the same
  # auth token. This setting determines how far apart the requests can be while
  # still using the same auth token.
  #config.batch_request_buffer_throttle = 5.seconds
  # This route will be the prefix for all oauth2 redirect callbacks. For
  # example, using the default '/omniauth', the github oauth2 provider will
  # redirect successful authentications to '/omniauth/github/callback'
  # config.omniauth_prefix = "/omniauth"
end

有什么想法如何解决？为什么这仅在生产中发生？

Answer 1

根据文档，您需要将config.secret_key = 'my secret key'添加到

config/initializers/devise_token_auth.rb

fwiw，您可能不想将秘密保存在代码中。使用

config.secret_key = ENV[ 'DEVISE_TOKEN_AUTH_SECRET_KEY' ]

编辑：我认为问题是您需要设置Devise.secret_key，而不是设计代币的秘密密钥。是否有设计初始化器？

Answer 2

您将其添加到DeviseTokenAuth初始化器中。而是创建一个Devise初始器config/initializers/devise.rb：

Devise.setup do |config|
  config.secret_key = '...'
end

注意1：您可以运行rake secret以获取一个随机的秘密钥匙下降到那里。

注2：优雅的人可能更喜欢将其秘密保存在环境变量中，以免将其检查到git中：

config.secret_key = ENV['DEVISE_SECRET_KEY'] if Rails.env.production?