Suggestion: resque-scheduler support?

[josh-m-sharpe]

This might be out of left field and way out of scope.

Could this gem support running an instance of resque-scheduler alongside various workers?

Asking because resque-scheduler takes up nearly as much memory as a standard worker but never does "real" work. So a fork for it as part of the pool might significantly reduce its memory footprint.

Maybe?

[nevans]

It's a good idea! I personally use don't use resque-scheduler. I just use cron jobs (using busybox cron!) that do no more than e.g. "script/resque_enqueue CronJobs::Hourly", etc. But there are benefits to scheduler, so a PR would probably be accepted (eventually... I'm bad at punctuality).

[nevans]

I might get around to this before the end of the year, but... I probably won't. 😉 I am going to migrate my biggest resque-pool deployment from simple cron jobs to resque-scheduler. And resque-scheduler should absolutely be part of a "batteries-included" resque deployment. But... many other projects still take priority over this, for me.

PRs are welcome! 🙂