V
V
Viktor Vsk2014-08-07 00:41:57
Ruby on Rails
Viktor Vsk, 2014-08-07 00:41:57

rails. How to debug Devise?

There is a project on Rails 3.2, Spree 1.3
It has resque. The resque
admin is connected by a simple:
mount Resque::Server, :at => "/resque"
( it does not matter, in the spre routes ( Spree::Core::Engine.routes.prepend do ... ), at the beginning of the config or at the end. )
But when you go to the address of the admin panel, everything works and is shown, only the user's login is reset.
The most interesting thing: this behavior is observed only on the production server (namely, the server, not the environment, since there is no such thing locally in production). Local machine - Ubuntu 14.04, server - Debian 6
Everything that is visible in the logs:

Started GET "/admin/resque" for xx.xx.xx.xx at 2014-08-07 01:39:17 +0400
Started GET "/admin/resque/overview" for xx.xx.xx.xx at 2014-08-07 01:39:17 +0400

ActionController::RoutingError (No route matches [GET] "/admin/resque/overview"):

Considering that everything works locally (and in production too), I can’t understand what else the environment may differ in. I don’t know how and where you can see how the device behaves (it is he who terminates the session for some unknown reason)
As I understand it, the admin panel itself is like this: https://github.com/resque/resque-web

Answer the question

In order to leave comments, you need to log in

1 answer(s)
S
Sergey Krasnodemsky, 2014-08-07
@Prognosticator

You can't tell from the question whether devise authentication doesn't work, or don't go to the resque admin panel.
Familiar symptoms, add a list of used gems, let's try to figure it out.
Redis running on the server?

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question