Visualizer for Repsheet

shared base for request_handler using dry-* gems

RequestHeader gives you per-req global header storage.

Rack middleware for logging web requests to a MongoDB database. Provides a profiler for monitoring logging overhead.

Formatters, parsers, and submitters for test results

Print formatted docs with Winpos WP-800

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.

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

response_for allows you to decorate the respond_to block of actions on subclassed controllers.

Easy to use response state pattern

With this gem you will be able to enqueue your emails on your Resque workers to avoid making your user wait for the email to be send when he causes an email sending action in your application. Using resque_action_mailer_backend makes email sending a breeze as you will be able to use Resque to retry failed emails, easily deliver all those marketing emails to your clients and without changing anything at your email sending code. Just tell your application to use :resque for sending emails and you're done, no need to add yet another tool just for delivering your emails if you're already using Resque for your asynchronous processing.

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.

Adds event publishing and job tracking ability to Resque

A management tool for resque workers. Allows spinning up and managing resque workers across multiple machines sharing the same Redis server