A Resque plugin. Provides a lightweight publish/subscribe messaging system, with message persistence when clients are down.

A Resque plugin. If you want only one instance of your job queued at a time, extend it with this module. For example: class ExampleJob extend Resque::Jobs::Queue::Lock def self.perform(repo_id) heavy_lifting end end

A resque plugin for specifying the priority between queues that workers use to determine what to work on next

A Resque plugin which allows you to create dedicated queues for jobs that use rate limited apis. These queues will pause when one of the jobs hits a rate limit, and unpause after a suitable time period. The rate_limited_queue can be used directly, and just requires catching the rate limit exception and pausing the queue. There are also additional queues provided that already include the pause/rety logic for twitter, angelist and evernote; these allow you to support rate limited apis with minimal changes.

resque plugin that allows you to attach information when a job is put in redis, and to do whatever you want with the information when it is popped off the resque queue

Compatible with Resque 1.x. Use Resque.push if you are using >= 2.x. Resque is great. So is job processing with redis. Our biggest drawback has been that resque requires the class that will be processing a job to be loaded when the job is enqueued. But what happens when the implementing job is defined in a separate application and isn't currently loaded into memory? Enter Resque Remote. Resque Remote's simple goal is to allow you to add a job to a queue with a string identifier for the class rather than the class constant. It is assumed that the worker-side of the equation _will_ have the class in memory and hence will be able to run it no problem. Feedback, comments and questions are welcome at bj [dot] neilsen [at] gmail [dot] com.

If you want to be able fetch the result from a Resque job's perform method. Results will be encoded using JSON. For example: require 'resque-result' class MyJob extend Resque::Plugins::Result def self.perform(meta_id, big_num) factor(big_num) end end meta0 = MyJob.enqueue(3574406403731) meta0.enqueued_at # => 'Wed May 19 13:42:41 -0600 2010' meta0.meta_id # => '03c9e1a045ad012dd20500264a19273c' # later meta1 = MyJob.get_meta('03c9e1a045ad012dd20500264a19273c') meta1.succeeded? # => true meta1.result # => [ 1299709, 2750159 ]

Deliver mail in a resque job

Telework is a Resque plugin aimed at controlling Resque workers from the web UI. It makes it easy to manage workers on a complex systems that may include several hosts, different queue(s) and an evolving source code that is deployed several times a day. Beyond starting and stopping workers on remote hosts, the plugin makes it easy to switch between code revisions, gives a partial view of each worker's log (stdout and stderr) and maintains a status of each workers.

top for Resque

Unique Resque queues using redis 1.6.0 scripting, sets and not much else

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

Utilities for using Resque in a Rails app

RhoConnect App Integration Server and related command-line utilities

A unified interface for various messaging queues

This plugin provides native instrumentation for collecting Resque metrics for queue, worker, working, failed, pending, and processed jobs.

Provides a simpler interface to enqueue Resque jobs between codebases without having to define the Jobs in multiple codebases.

Duck punch Resque to use active record for backround jobs instead of redis

Trinidad extension to autoconfigure and launch Resque

Uploadbox makes easy to manage files in your Rails application.