Project

Reverse Dependencies for resque

The projects listed here declare resque as a runtime or development dependency

0.01
No commit activity in last 3 years
No release in over 3 years
resque-exceptional provides a Resque failure backend that sends exceptions raised by jobs to getexceptional.com.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
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.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
A Resque plugin that provides endpoints which distributes Jobs submitted to them to (multiple) subscribing queues. Useful for loosely coupled inter-application communication.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No release in over 3 years
Handles establishing and disconnecting db connections when running Resque on Heroku cedar stack.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
0.01
Low commit activity in last 3 years
No release in over a year
Seamless integration of resque with resque-progress and resque-lock
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No release in over 3 years
A Resque plugin to ensure unique workers while preventing queue starvation
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
0.01
No commit activity in last 3 years
No release in over 3 years
A simple mechanism to create custom log files based on queue names of Resque workers.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
A Rails engine port of the Sinatra app that is included in Chris Wanstrath's resque gem.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
A Resque plugin that provides helpers for progress updates from within your jobs. For example: class MyJob extend Resque::Plugins::Progress def self.perform(meta_id, *args) (0..10).each do |i| at(i, 10, "Lifted #{num} heavy things. #{10-num} more to go!") heavy_lifting(i) end end end meta0 = MyJob.enqueue('stuff') meta0.progress.num_complete # => 0 meta0.progress.total # => 10 meta0.progress.percent # => 100 meta0.progress.message # => nil # later meta1 = MyJob.get_meta('03c9e1a045ad012dd20500264a19273c') meta1.progress.num_complete # => 4 meta1.progress.total # => 10 meta1.progress.percent # => 40 meta1.progress.message # => 'Lifted 4 heavy things. 6 more to go!'
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
A Resque plugin. Provides a lightweight publish/subscribe messaging system, with message persistence when clients are down.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
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
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
A resque plugin for specifying the priority between queues that workers use to determine what to work on next
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
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 defined in a separate application and isn't currently loaded into memory? Enter Resque Remote. Resque Remote's simple goal is to allow you to add a job to a queue with a string identifier for the class rather than the class constant. It is assumed that the worker-side of the equation _will_ have the class in memory and hence will be able to run it no problem. Feedback, comments and questions are welcome at bj [dot] neilsen [at] gmail [dot] com.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
If you want to be able fetch the result from a Resque job's perform method. Results will be encoded using JSON. For example: require 'resque-result' class MyJob extend Resque::Plugins::Result def self.perform(meta_id, big_num) factor(big_num) end end meta0 = MyJob.enqueue(3574406403731) meta0.enqueued_at # => 'Wed May 19 13:42:41 -0600 2010' meta0.meta_id # => '03c9e1a045ad012dd20500264a19273c' # later meta1 = MyJob.get_meta('03c9e1a045ad012dd20500264a19273c') meta1.succeeded? # => true meta1.result # => [ 1299709, 2750159 ]
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.01
No commit activity in last 3 years
No release in over 3 years
Telework is a Resque plugin aimed at controlling Resque workers from the web UI. It makes it easy to manage workers on a complex systems that may include several hosts, different queue(s) and an evolving source code that is deployed several times a day. Beyond starting and stopping workers on remote hosts, the plugin makes it easy to switch between code revisions, gives a partial view of each worker's log (stdout and stderr) and maintains a status of each workers.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026