Resque-Web Alternative

[mlh758]

You've got a really great tool here that I use in several projects. Resque-Web itself didn't quite fit my needs since I wanted something that was a little more flexible to deploy in a containerized environment. I made this as an alternative. It doesn't have the extensibility for plugins like scheduler but it handles viewing your workers, queues, failures, and deleting failed jobs nicely.

I wanted to make sure you all were okay with it existing with that name and see if you had any feedback.

[glensc]

@mlh758 does your alternative solve this problem?:

• Redis::CommandError - CROSSSLOT Keys in request don't hash to the same slot #154

[mlh758]

Frankly I have no idea. Are you on the latest version of this library? The line number in the stack trace doesn't line up to the line number of the function of the same name in master. I don't think this is necessarily an issue with this resque_web gem. It seems like you're monitoring a Node project of a similar name with this Ruby project? The implementation of Resque web is tied pretty close to how the Resque gem is written. node-resque advertises API compatibility, but I don't know how this library could guarantee that.

You could try my project and see what happens, I've never tried to point it to a cluster... But I certainly won't make any guarantees.

[glensc]

@mlh758 yes, I tried with the latest gems, the error remains.

[glensc]

@mlh758 redis cluster support needed first: mlh758/resque-web-ish#8

[glensc]

No description provided.

[mlh758]

I edited the comment. You left that last comment in reply to something I posted a year ago, almost a year after I posted it.

[glensc]

@mlh758 and that's the exact point why must use permalinks. I left permalinks in my comment there which you can edit your comment with. and seems you didn't get the message if you keep making links to branches.

[mlh758]

I didn't get the message because I don't pay much attention to people swooping in with a copy pasta on year old comments unrelated to the issue being discussed. I was trying to be helpful answering your questions and pointing you to relevant code from my kitchen table at 10 PM.