- Does shonm/resque-bundle work with Laravel?
- No. shonm/resque-bundle is a Symfony bundle that registers through AppKernel and relies on YAML service definitions plus app/console commands, so there is no Laravel service provider, bundle loader, or console kernel for it to bind to. Its appearance in a Laravel catalog is a data-quality error rather than a usable dependency. For Laravel, use the native queue system with the Redis driver and Horizon instead.
- How do I install and configure shonm/resque-bundle?
- Install it with Composer alongside chrisboulton/php-resque, register the bundle in your Symfony AppKernel, and import its YAML configuration. That config covers the Redis connection details and the queue names your workers listen on. Jobs and workers are wired as container services, so you declare them in service configuration rather than in PHP attributes.
- How do I dispatch a background job with this bundle?
- You dispatch through the bundle's Symfony service, which delegates to php-resque to push a job onto a named queue. Application code supplies a job class and its arguments, and the entry sits in Redis until a worker picks it up. Because the payload is a PHP-serialized job object, refactoring that job class breaks entries already waiting in the queue.
- Which Laravel or PHP versions does shonm/resque-bundle support?
- None of the Laravel versions; its scope is the Symfony 2 and 3 era it was written for. The underlying chrisboulton/php-resque library carries no PHP 8.x commitment, and the bundle describes itself as not maintained. Treat any modern version claim as unverified and assume the code is unsafe on current runtimes.
- Is shonm/resque-bundle still maintained and safe for production?
- No. The bundle is unmaintained, its php-resque dependency is unmaintained, and it has roughly 12 stars with zero dependents, so there is no vendor to escalate to and no security patch path. It also ships no retries, scheduling, unique jobs, metrics, or failed-job UI. Adopting it means owning a fork of an abandoned wrapper around an abandoned engine.
- What should Laravel developers use instead of Resque?
- Use Laravel's native queue system with the Redis driver, plus Horizon for worker supervision, retries, metrics, and a failed-job dashboard. That stack is first-party, actively maintained, and closes the retry, scheduling, and observability gaps Resque leaves open. If you genuinely need cross-language queues, evaluate a maintained broker rather than a Resque wrapper.
- Does Resque guarantee job delivery if a worker crashes?
- No. Classic Resque pops a job off the queue before executing it, so a worker killed mid-job loses that job permanently, with no acknowledgement, visibility timeout, or redelivery. Any requirement for at-least-once processing fails this design outright. There is no built-in retry policy either, so failure handling depends on plugins from a largely abandoned ecosystem.
- What does it take to run Resque workers?
- The bundle exposes Symfony console commands for starting and managing workers, but the underlying model forks a child process per job, which depends on the pcntl extension and POSIX signals. Those are frequently unavailable or fragile under FPM, container, and managed-runtime setups. You also need a supervisor such as systemd or Supervisor to keep worker processes alive.
- How do I migrate existing Resque jobs to Laravel queues?
- Start by inventorying job classes, queue names, payload format, retry expectations, and the worker fleet. Because payloads are PHP-serialized objects, you must drain or translate in-flight entries before renaming or refactoring any job class. Then map each job onto a Laravel job class and stand up Horizon on the target stack; the migration estimate, not bundle adoption, is the useful deliverable.
- Can it exchange jobs with Ruby Resque or other Resque clients?
- Only in the narrow sense that it targets the same Redis-backed queue names as php-resque. Payloads are PHP-serialized job objects, so a Ruby Resque worker cannot meaningfully consume them without a compatible serializer on both sides. If cross-language interoperability is the real requirement, verify the payload format end to end before committing to this bundle.