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

where the wild things are. err, when resque gets stuck

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.

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!

Basic reservation system for Slack

Sinatra based web server that turns your sequel model directly into a RESTful API.

Start creating your awesome app straight away without worrying the nitty-gritties of HTTP call implementation.

Common classes and methods to handle rest communication

On MS Windows, restart runs your shell command, then re-runs it any time filesystem change is detected. For example, "restart ruby test.rb" will run "ruby test.rb", then re-run it after test.rb file changes (or any other files change in current working directory or any subdirectories under it).