A fast and functional (API and paradigm) HTTP client, using only Ruby's standard library as dependency. e.g: Net::HTTP and URI.

Based on padrino's ruby require code

Provides a convenience method to retry blocks of code that might fail due to temporary errors, e.g. a network service that becomes temporarily unavailable. The retries are timed to back-off exponentially (2^n seconds), hopefully giving time for the remote server to recover.

Ruby interface for the RescueTime Data Analytics API.

Rescues unique constraint violations and turns them into ActiveRecord errors

Make your reserved words on Rails

Ruby wrapper for easy interaction with a RESO Web API compliant server.

Supports Trestle, Spark, Bridge Interactive, MLS Grid

Allows communication with MLS systems conforming to the RESO Web API standard

For all of you, who prefer to add JS libraries via gem

Easy to use response state pattern

Easy to use response state pattern

There are a number of plugins which allow you define unique jobs, but each only handle on use-case. This allows you have full control over how uniqueness is defined

Normally resque processes queues in a fixed order. This can lead to jobs in queues at the end of the list not getting process for very long periods. resque-fairly provides a mechanism where by workers are distributed across the set of queues with pending jobs fairly. This results in a much mor...

A Resque plugin that provides endpoints which distributes Jobs submitted to them to (multiple) subscribing queues. Useful for loosely coupled inter-application communication.

Seamless integration of resque with resque-progress and resque-lock

Light weight job scheduling on top of Resque Mongo. Adds methods enqueue_at/enqueue_in to schedule jobs in the future. Also supports queueing jobs on a fixed, cron-like schedule.

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 ...

Deliver mail in a resque job

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