resque-mongo 1.8.1 → 1.9.8.1

data/.gitignore

@@ -1,3 +0,0 @@
-*.gemspec
-pkg
-nbproject

data/.kick

@@ -1,26 +0,0 @@
-# take control of the growl notifications
-module GrowlHacks
-  def growl(type, subject, body, *args, &block)
-    case type
-    when Kicker::GROWL_NOTIFICATIONS[:succeeded]
-      puts subject = "Success"
-      body = body.split("\n").last
-    when Kicker::GROWL_NOTIFICATIONS[:failed]
-      subject = "Failure"
-      puts body
-      body = body.split("\n").last
-    else
-      return nil
-    end
-    super(type, subject, body, *args, &block)
-  end
-end
-
-Kicker.send :extend, GrowlHacks
-
-# no logging
-Kicker::Utils.module_eval do
-  def log(message)
-    nil
-  end
-end

data/CONTRIBUTORS

@@ -1,32 +0,0 @@
-* Chris Wanstrath
-* gravis
-* scotttam
-* John Barnette
-* Mike Mangino
-* Rob Hanlon
-* Jason Amster
-* Aaron Quint
-* Adam Cooke
-* Ashley Martens
-* Matt Duncan
-* Michael Dwan
-* Daniel Ceballos
-* Roman Heinrich
-* Thibaut Barrère
-* jgeiger
-* Simon Rozet
-* Dave Hoover
-* Christos Trochalakis
-* Ben VandenBos
-* snusnu
-* Arthur Zapparoli
-* Ben Marini
-* Brian P O'Rourke
-* Jim Remsik and Les Hill
-* Karel Minarik
-* Luc Castera
-* Masatomo Nakano
-* Matt Palmer
-* PJ Hyett
-* Roland Moriz
-* malomalo

data/config.ru

@@ -1,14 +0,0 @@
-#!/usr/bin/env ruby
-require 'logger'
-
-$LOAD_PATH.unshift ::File.expand_path(::File.dirname(__FILE__) + '/lib')
-require 'resque/server'
-
-# Set the RESQUECONFIG env variable if you've a `resque.rb` or similar
-# config file you want loaded on boot.
-if ENV['RESQUECONFIG'] && ::File.exists?(::File.expand_path(ENV['RESQUECONFIG']))
-  load ::File.expand_path(ENV['RESQUECONFIG'])
-end
-
-use Rack::ShowExceptions
-run Resque::Server.new

data/deps.rip

@@ -1,8 +0,0 @@
-mongo
-bson_ext
-git://github.com/brianmario/yajl-ruby.git 0.6.3
-git://github.com/sinatra/sinatra.git 0.9.4
-git://github.com/rack/rack.git 1.0
-git://github.com/quirkey/vegas.git v0.1.2
-git://github.com/brynary/rack-test.git v0.5.3
-rake

data/docs/HOOKS.md

@@ -1,121 +0,0 @@
-Resque Hooks
-============
-
-You can customize Resque or write plugins using its hook API. In many
-cases you can use a hook rather than mess with Resque's internals.
-
-For a list of available plugins see
-<http://wiki.github.com/defunkt/resque/plugins>.
-
-
-Worker Hooks
-------------
-
-If you wish to have a Proc called before the worker forks for the
-first time, you can add it in the initializer like so:
-
-    Resque.before_first_fork do
-      puts "Call me once before the worker forks the first time"
-    end
-
-You can also run a hook before _every_ fork:
-
-    Resque.before_fork do |job|
-      puts "Call me before the worker forks"
-    end
-
-The `before_fork` hook will be run in the **parent** process. So, be
-careful - any changes you make will be permanent for the lifespan of
-the worker.
-
-And after forking:
-
-    Resque.after_fork do |job|
-      puts "Call me after the worker forks"
-    end
-
-The `after_fork` hook will be run in the child process and is passed
-the current job. Any changes you make, therefor, will only live as
-long as the job currently being processes.
-
-All worker hooks can also be set using a setter, e.g.
-
-    Resque.after_fork = proc { puts "called" }
-
-
-Job Hooks
----------
-
-Plugins can utilize job hooks to provide additional behavior. A job
-hook is a method name in the following format:
-
-    HOOKNAME_IDENTIFIER
-
-For example, a `before_perform` hook which adds locking may be defined
-like this:
-
-    def before_perform_with_lock(*args)
-      set_lock!
-    end
-
-Once this hook is made available to your job (either by way of
-inheritence or `extend`), it will be run before the job's `perform`
-method is called. Hooks of each type are executed in alphabetical order,
-so `before_perform_a` will always be executed before `before_perform_b`.
-An unnamed hook (`before_perform`) will be executed first.
-
-The available hooks are:
-
-* `before_perform`: Called with the job args before perform. If it raises
-  `Resque::Job::DontPerform`, the job is aborted. If other exceptions
-  are raised, they will be propagated up the the `Resque::Failure`
-  backend.
-
-* `after_perform`: Called with the job args after it performs. Uncaught
-  exceptions will propagate up to the `Resque::Failure` backend.
-
-* `around_perform`: Called with the job args. It is expected to yield in order
-  to perform the job (but is not required to do so). It may handle exceptions
-  thrown by `perform`, but any that are not caught will propagate up to the
-  `Resque::Failure` backend.
-
-* `on_failure`: Called with the exception and job args if any exception occurs
-  while performing the job (or hooks).
-
-Hooks are easily implemented with superclasses or modules. A superclass could
-look something like this.
-
-    class LoggedJob
-      def self.before_perform_log_job(*args)
-        Logger.info "About to perform #{self} with #{args.inspect}"
-      end
-    end
-
-    class MyJob < LoggedJob
-      def self.perform(*args)
-        ...
-      end
-    end
-
-Modules are even better because jobs can use many of them.
-
-    module LoggedJob
-      def before_perform_log_job(*args)
-        Logger.info "About to perform #{self} with #{args.inspect}"
-      end
-    end
-
-    module RetriedJob
-      def on_failure_retry(e, *args)
-        Logger.info "Performing #{self} caused an exception (#{e}). Retrying..."
-        Resque.enqueue self, *args
-      end
-    end
-
-    class MyJob
-      extend LoggedJob
-      extend RetriedJob
-      def self.perform(*args)
-        ...
-      end
-    end

data/docs/PLUGINS.md

@@ -1,93 +0,0 @@
-Resque Plugins
-==============
-
-Resque encourages plugin development. For a list of available plugins,
-please see <http://wiki.github.com/defunkt/resque/plugins>.
-
-The `docs/HOOKS.md` file included with Resque documents the available
-hooks you can use to add or change Resque functionality. This document
-describes best practice for plugins themselves.
-
-
-Version
--------
-
-Plugins should declare the major.minor version of Resque they are
-known to work with explicitly in their README.
-
-For example, if your plugin depends on features in Resque 2.1, please
-list "Depends on Resque 2.1" very prominently near the beginning of
-your README.
-
-Because Resque uses [Semantic Versioning][sv], you can safely make the
-following assumptions:
-
-* Your plugin will work with 2.2, 2.3, etc - no methods will be
-  removed or changed, only added.
-* Your plugin might not work with 3.0+, as APIs may change or be
-  removed.
-
-
-Namespace
----------
-
-All plugins should live under the `Resque::Plugins` module to avoid
-clashing with first class Resque constants or other Ruby libraries.
-
-Good:
-
-* Resque::Plugins::Lock
-* Resque::Plugins::FastRetry
-
-Bad:
-
-* Resque::Lock
-* ResqueQueue
-
-
-Gem Name
---------
-
-Gem names should be in the format of `resque-FEATURE`, where `FEATURE`
-succinctly describes the feature your plugin adds to Resque.
-
-Good:
-
-* resque-status
-* resque-scheduler
-
-Bad:
-
-* multi-queue
-* defunkt-resque-lock
-
-
-Hooks
------
-
-Job hook names should be namespaced to work properly.
-
-Good:
-
-* before_perform_lock
-* around_perform_check_status
-
-Bad:
-
-* before_perform
-* on_failure
-
-
-Lint
-----
-
-Plugins should test compliance to this document using the
-`Resque::Plugin.lint` method.
-
-For example:
-
-    assert_nothing_raised do
-      Resque::Plugin.lint(Resque::Plugins::Lock)
-    end
-
-[sv]: http://semver.org/

data/examples/async_helper.rb

@@ -1,31 +0,0 @@
-# If you want to just call a method on an object in the background,
-# we can easily add that functionality to Resque.
-#
-# This is similar to DelayedJob's `send_later`.
-#
-# Keep in mind that, unlike DelayedJob, only simple Ruby objects
-# can be persisted.
-#
-# If it can be represented in JSON, it can be stored in a job.
-
-# Here's our ActiveRecord class
-class Repository < ActiveRecord::Base
-  # This will be called by a worker when a job needs to be processed
-  def self.perform(id, method, *args)
-    find(id).send(method, *args)
-  end
-
-  # We can pass this any Repository instance method that we want to
-  # run later.
-  def async(method, *args)
-    Resque.enqueue(Repository, id, method, *args)
-  end
-end
-
-# Now we can call any method and have it execute later:
-
-@repo.async(:update_disk_usage)
-
-# or
-
-@repo.async(:update_network_source_id, 34)

data/examples/demo/README.markdown

@@ -1,71 +0,0 @@
-Resque Demo
------------
-
-This is a dirt simple Resque setup for you to play with.
-
-
-### Starting the Demo App
-
-Here's how to run the Sinatra app:
-
-    $ git clone git://github.com/defunkt/resque.git
-    $ cd resque/examples/demo
-    $ rackup config.ru
-    $ open http://localhost:9292/
-
-Click 'Create New Job' a few times. You should see the number of
-pending jobs rising.
-  
-
-### Starting the Demo Worker
-
-Now in another shell terminal start the worker:
-
-    $ cd resque/examples/demo
-    $ VERBOSE=true QUEUE=default rake resque:work
-
-You should see the following output:
-
-    *** Starting worker hostname:90185:default
-    *** got: (Job{default} | Demo::Job | [{}])
-    Processed a job!
-    *** done: (Job{default} | Demo::Job | [{}])
-
-You can also use `VVERBOSE` (very verbose) if you want to see more:
-
-    $ VERBOSE=true QUEUE=default rake resque:work
-    *** Starting worker hostname:90399:default
-    ** [05:55:09 2009-09-16] 90399: Registered signals
-    ** [05:55:09 2009-09-16] 90399: Checking default
-    ** [05:55:09 2009-09-16] 90399: Found job on default
-    ** [05:55:09 2009-09-16] 90399: got: (Job{default} | Demo::Job | [{}])
-    ** [05:55:09 2009-09-16] 90399: resque: Forked 90401 at 1253141709
-    ** [05:55:09 2009-09-16] 90401: resque: Processing default since 1253141709
-    Processed a job!
-    ** [05:55:10 2009-09-16] 90401: done: (Job{default} | Demo::Job | [{}])
-
-Notice that our workers `require 'job'` in our `Rakefile`. This
-ensures they have our app loaded and can access the job classes.
-
-
-### Starting the Resque frontend
-
-Great, now let's check out the Resque frontend. Either click on 'View
-Resque' in your web browser or run:
-
-    $ open http://localhost:9292/resque/
-    
-You should see the Resque web frontend. 404 page? Don't forget the
-trailing slash!
-
-
-### config.ru
-
-The `config.ru` shows you how to mount multiple Rack apps. Resque
-should work fine on a subpath - feel free to load it up in your
-Passenger app and protect it with some basic auth.
-
-
-### That's it!
-
-Click around, add some more queues, add more jobs, do whatever, have fun.

data/examples/demo/Rakefile

@@ -1,8 +0,0 @@
-$LOAD_PATH.unshift File.dirname(__FILE__) + '/../../lib'
-require 'resque/tasks'
-require 'job'
-
-desc "Start the demo using `rackup`"
-task :start do 
-  exec "rackup config.ru"
-end

data/examples/demo/app.rb

@@ -1,38 +0,0 @@
-require 'sinatra/base'
-require 'resque'
-require 'job'
-
-module Demo
-  class App < Sinatra::Base
-    get '/' do
-      info = Resque.info
-      out = "<html><head><title>Resque Demo</title></head><body>"
-      out << "<p>"
-      out << "There are #{info[:pending]} pending and "
-      out << "#{info[:processed]} processed jobs across #{info[:queues]} queues."
-      out << "</p>"
-      out << '<form method="POST">'
-      out << '<input type="submit" value="Create New Job"/>'
-      out << '&nbsp;&nbsp;<a href="/resque/">View Resque</a>'
-      out << '</form>'
-      
-       out << "<form action='/failing' method='POST''>"
-       out << '<input type="submit" value="Create Failing New Job"/>'
-       out << '&nbsp;&nbsp;<a href="/resque/">View Resque</a>'
-       out << '</form>'
-      
-      out << "</body></html>"
-      out
-    end
-
-    post '/' do
-      Resque.enqueue(Job, params)
-      redirect "/"
-    end
-    
-    post '/failing' do 
-      Resque.enqueue(FailingJob, params)
-      redirect "/"
-    end
-  end
-end