-
Notifications
You must be signed in to change notification settings - Fork 481
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
Cannot Show Tabs on resque-web #432
Comments
+1 for me (gem 'resque-scheduler', '~> 3.0.0') |
@melalj this solve my problem require 'resque/scheduler/server'
Awesome::Application.routes.draw do
# ...
constraint = lambda { ... }
constraints constraint do
mount Resque::Server.new, at: '/resque_web', as: :resque_web
end
end |
@zzet That worked for me too +1 |
This issue is caused by a change in the architecture of Resque-web (https://github.com/resque/resque-web/blob/master/PLUGINS.md). I started porting the old Sinatra based code over to being a Rails engine, but have run into a snag: to test the engine, it needs to be mounted into a dummy Rails app, so the gemspec needs to include Rails and the resque-web engine. Trouble is, this also pulls in Minitest 5 as a dependency. Test::Unit seems to be incompatible with Minitest 5, so the tests will no longer run. It looks like the only way forwards may be to port the test suite over to use Minitest. I'm happy to begin work on this if people agree it's the correct approach? |
I've finished this work now, so the Delayed and Schedule tabs show up in the new Resque Web as they should if you use the code referred to in this PR: #464 I didn't do much more than port over the code as it stood with as few changes as possible, so comments and testing are appreciated. It probably needs a few more tests in there as a couple of places turned out to have quite sparse coverage. |
I followed all instructions on the README to show up the "Delayed" and "Schedule" tabs on the resque-web interface, but nothing!
Here's the imported gems:
To normally add scheduler to resque-web, I edited the
./config/initializers/resque_config.rb
To load resque-web, I have used a rails route:
But still, no effect on resque web interface... Any clue?
The text was updated successfully, but these errors were encountered: