Remotely enqueueing and dequeueing jobs across Redis namespaces should be simpler. BJ Neilsen laid a solid foundation for this gem, which is forked off of his gem resque-remote. That said, these two gems provide a different set of methods for remote enqueueing and dequeueing. If all you need is remote enqueueing within the same namespace, use resque-remote.

Make your custom reports to CSV in background using Resque with simple DSL

Coverts hash and ActiveRecord objects to minimal repersentations for resque to use

Ensures that only one Resque job with unique arguments is running at a time.

Declare resque queues serial and jobs in that queue will be run in serial mode

Integration of resque with resque-progress and resque-lock

Resque::Failure back-end which sends a Slack message whenever a Resque worker fails.

Sliding Window unique-job workflow for Resque jobs

A Resque failure backend for http://squash.io

This will stagger your resque jobs over a configurable duration rather then enqueueing them all together

Start and manage multiple resque workers.

Resque plugin that pushes the job statistics to statsd

Adds support for futures to resque-status

Set time limits on Resque jobs per Job class.

Configure resque-unique_in_queue and resque-unique_at_runtime uniqueness by arity of perform method, with automated cleanup tools

A resque plugin that ensures job uniqueness at enqueue time.

resque_unit(without mock)

A stripped version of the Resque web interface that's safe to use by not so trustworthy personnel. You get all the same information as the regular interface, but can't delete or retry anything.

Automatically kill a child of resque worker based on max memory.

Reduce your redundant gem depenencies with resquire, which figures out which gems are redundant so you can require less gems for your ruby projects while still retaining the same functionality! By reducing redundant gems, you can make your application faster!