Need help with php-resque?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

3.5K Stars 792 Forks MIT License 329 Commits 103 Opened issues


PHP port of resque (Workers and Queueing)

Services available


Need anything else?

Contributors list

php-resque: PHP Resque Worker (and Enqueue) Build Status

Resque is a Redis-backed library for creating background jobs, placing those jobs on one or more queues, and processing them later.


Resque was pioneered and is developed by the fine folks at GitHub (yes, I am a kiss-ass), and written in Ruby. What you're seeing here is an almost direct port of the Resque worker and enqueue system to PHP.

For more information on Resque, visit the official GitHub project:

For further information, see the launch post on the GitHub blog:

The PHP port does NOT include its own web interface for viewing queue stats, as the data is stored in the exact same expected format as the Ruby version of Resque.

The PHP port provides much the same features as the Ruby version:

  • Workers can be distributed between multiple machines
  • Includes support for priorities (queues)
  • Resilient to memory leaks (forking)
  • Expects failure

It also supports the following additional features:

  • Has the ability to track the status of jobs
  • Will mark a job as failed, if a forked child running a job does not exit with a status code as 0
  • Has built in support for
    methods, called pre and post jobs


  • PHP 5.3+
  • Redis 2.2+
  • Optional but Recommended: Composer

Getting Started

The easiest way to work with php-resque 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 to your application's composer.json.
    "require": {
        "chrisboulton/php-resque": "1.2.x"
  1. Run

    composer install
  2. If you haven't already, add the Composer autoload to your project's initialization file. (example)

require 'vendor/autoload.php';


Queueing Jobs

Jobs are queued as follows:

// Required if redis is located elsewhere

$args = array( 'name' => 'Chris' ); Resque::enqueue('default', 'My_Job', $args);

Defining Jobs

Each job should be in its own class, and include a

class My_Job
    public function perform()
        // Work work work
        echo $this->args['name'];

When the job is run, the class will be instantiated and any arguments will be set as an array on the instantiated object, and are accessible via


Any exception thrown by a job will result in the job failing - be careful here and make sure you handle the exceptions that shouldn't result in a job failing.

Jobs can also have

methods. If a
method is defined, it will be called before the
method is run. The
method, if defined, will be called after the job finishes.
class My_Job
    public function setUp()
        // ... Set up environment for this job

public function perform()
    // .. Run job

public function tearDown()
    // ... Remove environment for this job


Dequeueing Jobs

This method can be used to conveniently remove a job from a queue.

// Removes job class 'My_Job' of queue 'default'
Resque::dequeue('default', ['My_Job']);

// Removes job class 'My_Job' with Job ID '087df5819a790ac666c9608e2234b21e' of queue 'default' Resque::dequeue('default', ['My_Job' => '087df5819a790ac666c9608e2234b21e']);

// Removes job class 'My_Job' with arguments of queue 'default' Resque::dequeue('default', ['My_Job' => array('foo' => 1, 'bar' => 2)]);

// Removes multiple jobs Resque::dequeue('default', ['My_Job', 'My_Job2']);

If no jobs are given, this method will dequeue all jobs matching the provided queue.

// Removes all jobs of queue 'default'

Tracking Job Statuses

php-resque has the ability to perform basic status tracking of a queued job. The status information will allow you to check if a job is in the queue, is currently being run, has finished, or has failed.

To track the status of a job, pass

as the fourth argument to
. A token used for tracking the job status will be returned:
$token = Resque::enqueue('default', 'My_Job', $args, true);
echo $token;

To fetch the status of a job:

$status = new Resque_Job_Status($token);
echo $status->get(); // Outputs the status

Job statuses are defined as constants in the

class. Valid statuses include:
  • Resque_Job_Status::STATUS_WAITING
    - Job is still queued
  • Resque_Job_Status::STATUS_RUNNING
    - Job is currently running
  • Resque_Job_Status::STATUS_FAILED
    - Job has failed
  • Resque_Job_Status::STATUS_COMPLETE
    - Job is complete
  • false
    - Failed to fetch the status - is the token valid?

Statuses are available for up to 24 hours after a job has completed or failed, and are then automatically expired. A status can also forcefully be expired by calling the

method on a status class.


Workers work in the exact same way as the Ruby workers. For complete documentation on workers, see the original documentation.

A basic "up-and-running"

file is included that sets up a running worker environment. (
when installed via Composer)

The exception to the similarities with the Ruby version of resque is how a worker is initially setup. To work under all environments, not having a single environment such as with Ruby, the PHP port makes no assumptions about your setup.

To start a worker, it's very similar to the Ruby version:

$ QUEUE=file_serve php bin/resque

It's your responsibility to tell the worker which file to include to get your application underway. You do so by setting the

environment variable:
$ QUEUE=file_serve APP_INCLUDE=../application/init.php php bin/resque

Pro tip: Using Composer? More than likely, you don't need to worry about

, because hopefully Composer is responsible for autoloading your application too!

Getting your application underway also includes telling the worker your job classes, by means of either an autoloader or including them.

Alternately, you can always

from your application and skip setting
altogether. Just be sure the various environment variables are set (
) before you do.


The port supports the same environment variables for logging to STDOUT. Setting

will print basic debugging information and
will print detailed information.
$ VERBOSE=1 QUEUE=file_serve bin/resque
$ VVERBOSE=1 QUEUE=file_serve bin/resque

Priorities and Queue Lists

Similarly, priority and queue list functionality works exactly the same as the Ruby workers. Multiple queues should be separated with a comma, and the order that they're supplied in is the order that they're checked in.

As per the original example:

$ QUEUE=file_serve,warm_cache bin/resque


queue will always be checked for new jobs on each iteration before the
queue is checked.

Running All Queues

All queues are supported in the same manner and processed in alphabetical order:

$ QUEUE='*' bin/resque

Running Multiple Workers

Multiple workers can be launched simultaneously by supplying the

environment variable:
$ COUNT=5 bin/resque

Be aware, however, that each worker is its own fork, and the original process will shut down as soon as it has spawned

forks. If you need to keep track of your workers using an external application such as
, you'll need to work around this limitation.

Custom prefix

When you have multiple apps using the same Redis database it is better to use a custom prefix to separate the Resque data:

$ PREFIX=my-app-name bin/resque


Similarly to the Ruby versions, supported platforms will immediately fork after picking up a job. The forked child will exit as soon as the job finishes.

The difference with php-resque is that if a forked child does not exit nicely (PHP error or such), php-resque will automatically fail the job.


Signals also work on supported platforms exactly as in the Ruby version of Resque:

  • QUIT
    - Wait for job to finish processing then exit
  • TERM
    - Immediately kill job then exit
  • USR1
    - Immediately kill job but don't exit
  • USR2
    - Pause worker, no new jobs will be processed
  • CONT
    - Resume worker.

Process Titles/Statuses

The Ruby version of Resque has a nifty feature whereby the process title of the worker is updated to indicate what the worker is doing, and any forked children also set their process title with the job being run. This helps identify running processes on the server and their resque status.

PHP does not have this functionality by default until 5.5.

A PECL module ( exists that adds this functionality to PHP before 5.5, so if you'd like process titles updated, install the PECL module as well. php-resque will automatically detect and use it.

Event/Hook System

php-resque has a basic event system that can be used by your application to customize how some of the php-resque internals behave.

You listen in on events (as listed below) by registering with

and supplying a callback that you would like triggered when the event is raised:
Resque_Event::listen('eventName', [callback]);

may be anything in PHP that is callable by
  • A string with the name of a function
  • An array containing an object and method to call
  • An array containing an object and a static method to call
  • A closure (PHP 5.3+)

Events may pass arguments (documented below), so your callback should accept these arguments.

You can stop listening to an event by calling

with the same arguments supplied to

It is up to your application to register event listeners. When enqueuing events in your application, it should be as easy as making sure php-resque is loaded and calling


When running workers, if you run workers via the default

script, your
script should initialize and register any listeners required for operation. If you have rolled your own worker manager, then it is again your responsibility to register listeners.

A sample plugin is included in the




Called once, as a worker initializes. Argument passed is the instance of

that was just initialized.


Called before php-resque forks to run a job. Argument passed contains the instance of

for the job about to be run.

is triggered in the parent process. Any changes made will be permanent for as long as the worker lives.


Called after php-resque forks to run a job (but before the job is run). Argument passed contains the instance of

for the job about to be run.

is triggered in the child process after forking out to complete a job. Any changes made will only live as long as the job is being processed.


Called before the

methods on a job are run. Argument passed contains the instance of
for the job about to be run.

You can prevent execution of the job by throwing an exception of

. Any other exceptions thrown will be treated as if they were thrown in a job, causing the job to fail.


Called after the

methods on a job are run. Argument passed contains the instance of
that was just run.

Any exceptions thrown will be treated as if they were thrown in a job, causing the job to be marked as having failed.


Called whenever a job fails. Arguments passed (in this order) include:

  • Exception - The exception that was thrown when the job failed
  • Resque_Job - The job that failed


Called immediately before a job is enqueued using the

method. Arguments passed (in this order) include:
  • Class - string containing the name of the job to be enqueued
  • Arguments - array of arguments for the job
  • Queue - string containing the name of the queue the job is to be enqueued in
  • ID - string containing the token of the job to be enqueued

You can prevent enqueing of the job by throwing an exception of



Called after a job has been queued using the

method. Arguments passed (in this order) include:
  • Class - string containing the name of scheduled job
  • Arguments - array of arguments supplied to the job
  • Queue - string containing the name of the queue the job was added to
  • ID - string containing the new token of the enqueued job


For a more in-depth look at what php-resque does under the hood (without needing to directly examine the code), have a look at


Project Lead

  • @chrisboulton


  • @acinader
  • @ajbonner
  • @andrewjshults
  • @atorres757
  • @benjisg
  • @cballou
  • @chaitanyakuber
  • @charly22
  • @CyrilMazur
  • @d11wtq
  • @danhunsaker
  • @dceballos
  • @ebernhardson
  • @hlegius
  • @hobodave
  • @humancopy
  • @iskandar
  • @JesseObrien
  • @jjfrey
  • @jmathai
  • @joshhawthorne
  • @KevBurnsJr
  • @lboynton
  • @maetl
  • @matteosister
  • @MattHeath
  • @mickhrmweb
  • @Olden
  • @patrickbajao
  • @pedroarnal
  • @ptrofimov
  • @rajibahmed
  • @richardkmiller
  • @Rockstar04
  • @ruudk
  • @salimane
  • @scragg0x
  • @scraton
  • @thedotedge
  • @tonypiper
  • @trimbletodd
  • @warezthebeef

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.