Weave Code
Resque Bundle Laravel Package
instasent/resque-bundle
A Symfony bundle for integrating Resque with PHP applications, providing configuration and services to dispatch, manage, and run Redis-backed background jobs so time-consuming tasks can be offloaded from web requests.
The resque bundle provides integration of php-resque to Symfony2. It is inspired from resque, a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.
Frequently asked questions about Resque Bundle
- Can I install instasent/resque-bundle in a Laravel application?
- Composer may install it, but it will not boot as a Laravel package. The package ships a Symfony Bundle subclass, a dependency-injection extension, and ContainerAwareCommand console commands, and Laravel has no bundle registration mechanism. Only its underlying chrisboulton/php-resque dependency is framework-agnostic and reusable.
- Is instasent/resque-bundle a Laravel package or a Symfony bundle?
- It is a Symfony2 bundle that wires Resque into Symfony applications. It provides Symfony service container integration, configuration-driven Redis settings, and Symfony console worker commands. It does not provide a Laravel service provider, publishable config, or queue driver.
- Does instasent/resque-bundle support Laravel 10 or Laravel 11?
- No. The bundle targets Symfony 2.x, which reached end of life in November 2018, and it has no Laravel version constraints or framework integration. You cannot expect it to register services or boot inside a modern Laravel application. Treat Laravel support as effectively zero.
- What Laravel queue setup should I use instead of instasent/resque-bundle?
- Use Laravel's native Redis queue driver with Horizon. It provides Redis-backed lists, multiple named queues, supervised workers, retries with backoff, metrics, and a dashboard with first-class framework support. It adds no new dependencies and avoids the abandoned Symfony2 stack. The native path dominates unless Resque wire-format compatibility is a hard external requirement.
- Does instasent/resque-bundle work with PHP 8?
- Probably not. Symfony2-era code commonly relies on each(), create_function, non-typed container signatures, and dynamic properties, all of which are removed or deprecated in PHP 8. Expect fatal errors on modern runtimes, and verify rather than assume. Any PHP version requirement of 8.0 or higher likely disqualifies the bundle outright.
- Is instasent/resque-bundle maintained and safe for production?
- The maintenance signals are poor: roughly 4 stars, 0 dependents, and a score near 0.14. The 2021-11-30 release date is almost certainly a metadata or tag artifact rather than evidence of active maintenance, since the codebase predates it by years. There is no credible security-response channel, and the unmaintained transitive dependency graph carries high supply-chain risk.
- How do I run Resque workers in Laravel without a Symfony bundle?
- The bundle's worker commands are Symfony Console commands wired through Symfony's Kernel and ContainerAwareCommand, so they do not exist in Laravel. In Laravel you would write an Artisan command or queue worker around chrisboulton/php-resque, or use Laravel's native queue worker instead. Either way, you own the supervisor configuration and fork-safety handling.
- How does php-resque forking affect Laravel database connections and container state?
- php-resque forks a child process per job, so inherited PDO connections, open file handles, and container state cross the fork boundary. That is a well-known source of duplicate-consumption and stale-connection bugs. You must add explicit reconnect logic and avoid relying on pre-fork container state inside jobs.
- Can instasent/resque-bundle interoperate with Ruby Resque workers or resque-web?
- Only indirectly. The bundle is Symfony configuration and service wiring over php-resque, so any Ruby Resque interoperability comes from php-resque's wire format, not from the bundle itself. If Resque wire compatibility is a contractual constraint, evaluate chrisboulton/php-resque directly with your own wrapper. Do not adopt the bundle just for that capability.
- How do I migrate from instasent/resque-bundle to Laravel queues?
- Rewrite each job payload as a Laravel Job class, configure the Redis queue connection, and run workers under Horizon or Supervisor. The work is largely mechanical if the number of job types is small. Choose this path unless Resque wire compatibility is mandatory; the native queue layer is supported, observable, and already integrated with Laravel.
Weaver
How can I help you explore Laravel packages today?