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
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.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
0.01
Repository is archived
No commit activity in last 3 years
No release in over 3 years
Make Active Record instance methods asynchronous using resque.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
0.01
No commit activity in last 3 years
No release in over 3 years
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
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
0.01
No commit activity in last 3 years
No release in over 3 years
A simple event bus on top of Resque. Publish and subscribe to events as they occur through a queue.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
0.01
A long-lived project that still receives updates
Resque queue backed by database audits, with automatic retry
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
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
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
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
0.01
Repository is gone
No release in over 3 years
Use the power of forking to run multiple Resque workers.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
 Popularity
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
 Popularity
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
 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
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