diff --git a/README.md b/README.md index 097de2b..e16b3a9 100644 --- a/README.md +++ b/README.md @@ -17,6 +17,43 @@ Because the PHP port is almost a direct API copy of the Ruby version, it is also compatible with the web interface of the Ruby version, which provides the ability to view and manage delayed jobs. +## Requirements ## + +* PHP 5.3+ +* Redis 2.2+ +* PHP-Resque 1.2+ +* Optional but Recommended: Composer + +## Getting Started ## + +The easiest way to work with php-resque-scheduler is when it's installed as a +Composer package inside your project. Composer isn't strictly +required, but makes life a lot easier. + +If you're not familiar with Composer, please see . + +1. Add php-resque-scheduler to your application's composer.json. + + ```json + { + ... + "require": { + "chrisboulton/php-resque-scheduler": "dev-master", + "php": ">=5.3.0" + }, + ... + } + ``` + +2. Run `composer install`. + +3. If you haven't already, add the Composer autoload to your project's + initialization file. (example) + + ```php + require 'vendor/autoload.php'; + ``` + ## Delayed Jobs To quote the documentation for the Ruby resque-scheduler: @@ -24,12 +61,11 @@ To quote the documentation for the Ruby resque-scheduler: > Delayed jobs are one-off jobs that you want to be put into a queue at some point in the future. The classic example is sending an email: - require 'Resque/Resque.php'; - require 'ResqueScheduler/ResqueScheduler.php'; - - $in = 3600; - $args = array('id' => $user->id); - ResqueScheduler::enqueueIn($in, 'email', 'SendFollowUpEmail', $args); +```php +$in = 3600; +$args = array('id' => $user->id); +ResqueScheduler::enqueueIn($in, 'email', 'SendFollowUpEmail', $args); +``` The above will store the job for 1 hour in the delayed queue, and then pull the job off and submit it to the `email` queue in Resque for processing as soon as @@ -39,16 +75,15 @@ Instead of passing a relative time in seconds, you can also supply a timestamp as either a DateTime object or integer containing a UNIX timestamp to the `enqueueAt` method: - require 'Resque/Resque.php'; - require 'ResqueScheduler/ResqueScheduler.php'; - - $time = 1332067214; - ResqueScheduler::enqueueAt($time, 'email', 'SendFollowUpEmail', $args); +```php +$time = 1332067214; +ResqueScheduler::enqueueAt($time, 'email', 'SendFollowUpEmail', $args); - $datetime = new DateTime('2012-03-18 13:21:49'); - ResqueScheduler::enqueueAt(datetime, 'email', 'SendFollowUpEmail', $args); +$datetime = new DateTime('2012-03-18 13:21:49'); +ResqueScheduler::enqueueAt(datetime, 'email', 'SendFollowUpEmail', $args); +``` -NOTE: resque-scheduler does not guarantee a job will fire at the time supplied. +**Note:** resque-scheduler does not guarantee a job will fire at the time supplied. At the time supplied, resque-scheduler will take the job out of the delayed queue and push it to the appropriate queue in Resque. Your next available Resque worker will pick the job up. To keep processing as quick as possible, keep your @@ -61,9 +96,15 @@ worker is responsible for pulling items off the schedule/delayed queue and addin them to the queue for resque. This means that for delayed or scheduled jobs to be executed, the worker needs to be running. -A basic "up-and-running" resque-scheduler.php file is included that sets up a -running worker environment is included in the root directory. It accepts many -of the same environment variables as php-resque: +A basic "up-and-running" resque-scheduler file that sets up a running worker +environment is included in the bin/ directory. + +To start a worker, it's very similar to the Ruby version: +```sh +$ LOGGING=1 php bin/resque-scheduler +``` + +It accepts many of the same environment variables as php-resque: * `REDIS_BACKEND` - Redis server to connect to * `LOGGING` - Enable logging to STDOUT @@ -74,18 +115,15 @@ of the same environment variables as php-resque: * `PIDFILE` - Write the PID of the worker out to this file The resque-scheduler worker requires resque to function. The demo -resque-scheduler.php worker allows you to supply a `RESQUE_PHP` environment -variable with the path to Resque.php. If not supplied and resque is not already -loaded, resque-scheduler will attempt to load it from your include path -(`require_once 'Resque/Resque.php';'`) +resque-scheduler worker uses the Composer autoloader to load Resque.php. -It's easy to start the resque-scheduler worker using resque-scheduler.php: - $ RESQUE_PHP=../resque/lib/Resque/Resque.php php resque-scheduler.php +It's easy to start the resque-scheduler worker using the included demo: + $ bin/resque-scheduler ## Event/Hook System php-resque-scheduler uses the same event system used by php-resque and exposes -the following events. +the following additional events: ### afterSchedule @@ -100,9 +138,12 @@ of the job, the class name of the job, and the job's arguments. ## Contributors ## -* chrisboulton -* rayward -* atorres757 -* tonypiper -* biinari -* cballou \ No newline at end of file +* [chrisboulton](//github.com/chrisboulton) +* [rayward](//github.com/rayward) +* [atorres757](//github.com/atorres757) +* [tonypiper](//github.com/tonypiper) +* [biinari](//github.com/biinari) +* [cballou](//github.com/cballou) +* [danhunsaker](//github.com/danhunsaker) +* [evertharmeling](//github.com/evertharmeling) +* [stevelacey](//github.com/stevelacey) diff --git a/resque-scheduler.php b/bin/resque-scheduler old mode 100644 new mode 100755 similarity index 70% rename from resque-scheduler.php rename to bin/resque-scheduler index e061f0e..c95f419 --- a/resque-scheduler.php +++ b/bin/resque-scheduler @@ -1,18 +1,28 @@ +#!/usr/bin/env php