Skip to content
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

Notes for Resque 2.0 #31

Closed
ono opened this issue May 27, 2014 · 4 comments
Closed

Notes for Resque 2.0 #31

ono opened this issue May 27, 2014 · 4 comments

Comments

@ono
Copy link
Owner

ono commented May 27, 2014

Most code of this repo was written years ago and it made me cry when I read it again. I have been thinking of refactoring but probably it makes more sense to do that when Resque 2.0 is officially out (although I am not really sure about the schedule and scope...). I put some notes about things I want to fix here.

  • Split lib/resque_cleaner into several files
  • Rewrite server(sinatra) code and templates
  • Rewrite tests
  • Have a simpler README. Migrate information about the console to wiki.
@gerrywastaken
Copy link

:) I was glad to see that you had already created this issue. I have been looking for a version of resque-cleaner for the new version of Resque-web.

👍

@ono
Copy link
Owner Author

ono commented Jan 13, 2015

@gerrywastaken I haven't tried new version of Resque-web by myself. Does resque-cleaner still make sense with it? I might talk to the maintainer and ask if there is a possibility to merge this plugin(rewritten version) into it.

@gerrywastaken
Copy link

@ono Absolutely. The new resque web doesn't group failures by class and time or have any filtering for the failed jobs. It really doesn't have any of the features resque-cleaner provides.

@lukeasrodgers
Copy link

FWIW I think it is unlikely that resque 2.0 will be released any time soon, if ever.

@ono ono closed this as completed Jan 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants