Project

Reverse Dependencies for rspec

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

0.01
Repository is archived
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
2026
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
2026
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
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
Low commit activity in last 3 years
A long-lived project that still receives updates
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 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
A long-lived project that still receives updates
💎 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
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
This gem is deprecated! Please use right_api_client instead. The rest_connection gem simplifies the use of RESTful APIs. It currently has support for RightScale API 1.0 and 1.5.
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
Basic API implementation for REST Countries API http://restcountries.eu
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 pretty simple transfer daemon, controlled with a RESTful API
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
Simple REST server that focuses on resources instead of routes.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026