- Can I use mcfedr/resque-queue-driver-bundle in a Laravel application?
- No. It is a Symfony bundle that plugs a Resque driver into the Queue Manager Bundle, and it relies on Symfony bundle registration, dependency injection, configuration trees, and compiler passes that do not exist in Laravel. Laravel's queue contracts, connectors, and worker lifecycle are different, so Composer requiring it into a Laravel app will not give you a working queue driver. Use Laravel's native Redis driver or a custom connector instead.
- Does this Resque queue driver support Laravel 10 or Laravel 11?
- No. The bundle is Symfony-only and its last release was in 2018, so its PHP and Symfony constraints are likely capped at PHP 7.x and Symfony 2.8/3.x/4.x. Those constraints will conflict with Laravel 10 or 11, which require modern PHP 8.x runtimes. Even if Composer resolution were forced, the bundle has no Laravel service provider or queue connector integration.
- What PHP and Symfony versions does mcfedr/resque-queue-driver-bundle require?
- Expect PHP 7.x-era constraints and Symfony 2.8, 3.x, or 4.x pins based on the bundle's 2018 release timeline. You should verify the exact composer.json constraints before planning anything, because they will determine whether the package can even resolve in your project. It is not designed for Symfony 5/6/7 or PHP 8.1+ Laravel stacks.
- How do I install and configure this bundle in Symfony?
- Install it with Composer as mcfedr/resque-queue-driver-bundle, register the bundle in your Symfony kernel or bundles.php, and configure the Resque queue driver through the Queue Manager Bundle configuration. You will also need a Resque worker process and Redis available. This setup is Symfony-specific and does not translate into a Laravel installation recipe.
- Is mcfedr/resque-queue-driver-bundle still maintained?
- Treat it as abandoned. The last release was 2018-02-24, it has zero stars and zero dependents in the assessment, and there is no CVE monitoring, maintainer response path, or active community validation. Forking it means you permanently own maintenance and compatibility work.
- What should Laravel developers use instead of Resque and this bundle?
- Use Laravel's native Redis queue driver with Horizon for supervision, retries, metrics, and dashboards. That stack is actively maintained, fits Laravel's queue contracts, and avoids Symfony bundle machinery entirely. Only consider Resque interoperability if you have a hard requirement to share a Redis namespace with an existing Resque worker fleet.
- How can Laravel dispatch jobs to an existing Resque worker fleet?
- Write a small custom Laravel queue connector that pushes Resque-compatible JSON payloads, including class, args, queue, and id, onto the resque:queue:<name> Redis list. This captures the only genuinely useful part of the bundle without importing Symfony dependencies. Confirm whether the existing fleet is Ruby or PHP, and match its payload and retry semantics exactly.
- What Redis keys and payload format does Resque use compared with Laravel's Redis queue?
- Resque workers consume job payloads from Redis lists named like resque:queue:<name>, with JSON containing fields such as class, args, queue, and id. Laravel's Redis queue uses different keys, such as queues:default, queues:default:delayed, and queues:default:reserved, so the two systems share nothing by default. Any bridge must explicitly translate key names and payload shapes.
- Can I run Resque workers on AWS Fargate, Cloud Run, or Kubernetes?
- Be careful. Resque's traditional worker model forks a child process per job using pcntl and relies on long-running blocking Redis reads, which is often a poor fit for request-driven or tightly sandboxed container runtimes. Fargate and Cloud Run are generally not friendly to fork-per-job workers. Prefer a dedicated long-running worker service with pcntl available, or reimplement the processing model.
- How do I migrate from this Symfony bundle to Laravel queues and test the switch?
- Enumerate every job class and payload shape, map each to a Laravel ShouldQueue job, and run both consumers against the same Redis lists during a dual-consumer window using a shared payload contract. Then drain and decommission the Symfony workers and remove the bundle. Test with a staging Redis instance and a real Resque worker, load-test payload compatibility, failure and retry behavior, and keep the spike time-boxed before committing.