Can't use dedicated Redis instance

[rpdillon]

Previous version supported setting a custom Redis instance; this is useful in instances where Redis/Resque are used for many different things, and Redis memory exhaustion in one use case won't take down unrelated use cases.

Is there a plan to add back configuration of the Redis endpoint?

[bleonard]

We thought we were the only ones using that - and then we stopped using it.
I bet we can figure out how to put it back in.

Are you interested in taking a crack at it?

A few thoughts

I'm pretty sure it can all be done in the adapter

You would have a new variable that would be set like redis= (like the only one). but that woudlset an instance variable.

Then, we'd but a block around everything, especially enqueue and enqueue_at to the Resque.redis to be that instance if it was set. And then ensure to put it back. The use of redis in the callback really worked out for that too.

As I recall, we'd also have to do that same thing in the workers. Maybe mix it in if they call that redis= method.

Another alternative might be to put all of that business in a new adapter. That might be better.

Or maybe, setting that redis= does the mixin and then modifies itself to wrap (alias method chain) all it's own methods as described above. That would keep it all pretty contained but still in the same class to minimize divergence that another adapter might create.

[rpdillon]

When I get some bandwidth I'll set it up. Thanks for the fast response.