A Rails-based frontend to the Resque job queue system.

Capistrano plugin that integrates Resque server tasks.

resque-cleaner maintains the cleanliness of failed jobs on Resque.

Operational controls for Active Job

Makes sure that for special jobs, there can be only one job with the same workload in one queue. Example: class CacheSweeper include Resque::Plugins::UniqueJob @queue = :cache_sweeps def self.perform(article_id) # Cache Me If You Can... end end

Models and services for sufia

resque-cleaner maintains the cleanliness of failed jobs on Resque.

resque-cleaner maintains the cleanliness of failed jobs on Resque.

Makes sure that for special jobs, there can be only one job with the same workload in one queue. Example: class CacheSweeper include Resque::Plugins::UniqueJob @queue = :cache_sweeps def self.perform(article_id) # Cache Me If You Can... end end

This is the New Relic plugin for monitoring Resque developed by Railsware Inc.

Ruby Adapter for Raygun

Tracks jobs performed, failed, and the duration of the last 100 jobs for each job type.

Tracks jobs performed, failed, and the duration of the last 100 jobs for each job type.

Tracking exceptions for Rails application store them in database by exception_notification gem.

When your resque jobs are frequent and fast, the overhead of forking and running your after_fork might get too big.

A failure backend for Resque that sends events to Sentry

Allows access and use of BigBlueButton from a Ruby on Rails application

A resque plugin for specifying the queues a worker pulls from with wildcards, negations, or dynamic look up from redis

A Resque plugin. Adds locking, with optional timeout/deadlock handling to resque jobs. Using a `lock_timeout` allows you to re-acquire the lock should your worker fail, crash, or is otherwise unable to relase the lock. i.e. Your server unexpectedly looses power. Very handy for jobs that are recurring or may be retried.

A simple Resque plugin that times and saves some simple metrics for Resque jobs back into redis. Based on this system you could build some simple auto-scaling mechanism based on the speed and ETA of queues. Also includes a hook/callback mechanism for recording/sending the metrics to your favorite tool (AKA statsd/graphite).