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.

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.

ResourceFull provides a fully-compliant ActiveResource server implementation built on ActionController. Additionally, it provides RESTful parameter queryability, paging, sorting, separation of controller concerns, multiple formats (HTML, XML, JSON), CRUD access permissions, and API metadata.

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

Easy to use response state pattern

Easy to use response state pattern

This gem makes it possible to send mails asynchronously using Resque by simply rewriting `SomeMailer.some_mail(ar_resource, 1234).deliver` to `SomeMailer.async_deliver.some_mail(ar_resource, 1234)`. Using ActiveRecord objects as arguments to mailers is still possible. This is achieved by storing the class name and the record id as arguments in the Resque queue which will be transformed back to records by the mailer job and passed along to the mailer.

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

A simple event bus on top of Resque. Publish and subscribe to events as they occur through a queue.

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 more predictable mean time to handling for jobs in queues that are not the first in the list.

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

Auto-scale Heroku workers for Resque

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

A simple mechanism to create custom log files based on queue names of Resque workers.

💎 Ensures that for a given queue, only one worker is working on a job at any given time. Example: require 'resque/plugins/lonely_job' class StrictlySerialJob extend Resque::Plugins::LonelyJob @queue = :serial_work def self.perform # only one at a time in this block, no parallelism allowed for this # particular queue end end

Mock resque with threads

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