- Can I use mcfedr/resque-bundle in a Laravel app?
- No. mcfedr/resque-bundle is a Symfony bundle built around Symfony's kernel, dependency injection container, and config tree, so there is no service provider or facade bridge into Laravel's container. For a Laravel application, use Laravel's native Redis queue with Horizon, or integrate php-resque directly behind a Laravel service provider. Both reach the same Redis-backed background job destination without carrying Symfony-specific glue.
- How do I install mcfedr/resque-bundle with Composer?
- You install it with composer require mcfedr/resque-bundle, then register the bundle in your Symfony kernel or bundles.php and add a resque configuration block under config/packages. The package is distributed as a Symfony bundle, so installation assumes a Symfony application skeleton rather than a plain PHP or Laravel project. Check the repository's composer.json for the exact Symfony and PHP version constraints before running the command, because the bundle targets an older Symfony-era compatibility range.
- Does mcfedr/resque-bundle support PHP 8.2 and PHP 8.3?
- That is unverified. The bundle appears to be from the Symfony 2, 3, or 4 and PHP 7.x era, and current ext-redis plus PHP 8.2 or 8.3 compatibility is not documented. Treat PHP 8 support as a spike item: read composer.json constraints, run a clean install in a disposable container, and confirm the Redis client path before committing. If it fails, the glue code is small enough to reproduce with php-resque or a native Laravel queue.
- Which Symfony versions does mcfedr/resque-bundle support?
- The bundle is likely pinned to older Symfony releases, most plausibly the Symfony 2, 3, or 4 era, based on its age and packaging style. The repository does not advertise a current Symfony 6 or 7 compatibility matrix. Verify the require constraints in composer.json and test against the exact Symfony version you run; a bundle that registers services and console commands through the container must match the kernel and DI behavior of that major version.
- Which Resque runtime does mcfedr/resque-bundle wrap — Ruby Resque or php-resque?
- The bundle is a thin producer and worker-bootstrap layer, not the queue itself, and the documentation does not clearly state which Resque implementation it targets. Resque is originally a Ruby job system backed by Redis, so adopting it means either running Ruby worker processes alongside PHP or using a PHP reimplementation such as php-resque and accepting its divergences. Confirm the intended runtime, Redis client (ext-redis or Predis), and worker command before treating this as a go or no-go decision.
- Are Resque job payloads compatible between Ruby Resque and PHP producers?
- Resque jobs are JSON envelopes carrying a class name string plus positional arguments, so compatibility depends entirely on both sides agreeing on that contract. Renaming a class, changing a constructor signature, or reordering arguments silently breaks in-flight jobs, and because producers and workers deploy on separate cadences this is a deploy-ordering problem rather than a code-review problem. If you need Ruby interop, integrate at the payload contract level and version your job classes deliberately. Do not assume the bundle guarantees wire compatibility with the Ruby reference.
- Does mcfedr/resque-bundle support resque-scheduler, retries, and failure backends?
- Coverage is not documented, and the bundle appears to focus on enqueue and work rather than the wider Resque plugin ecosystem. resque-scheduler, retry plugins, and the failure backend are separate concerns that may need to be handled by the underlying Resque runtime or added yourself. Before adopting, list the exact features you need and verify each one in a spike against the runtime the bundle actually wraps.
- How should I supervise Resque workers in production?
- The bundle does not define a production topology, and there is no documented heartbeat or health signal, so worker supervision is your responsibility. The common approach is systemd or supervisord units that restart crashed workers and a deployment step that restarts workers after releasing new job class code. Plan for graceful shutdown so in-flight jobs finish, and monitor Redis queue depth plus failed-job counts as your primary health indicators.
- Is mcfedr/resque-bundle maintained and safe for production use?
- Signals point to high risk: roughly nine stars, zero dependents, and a single maintainer, which means effectively no production user base to surface breakage and a bus factor of one. Abandonment is the base case rather than a tail risk, and the bundle sits on a legacy Resque model that is feature-frozen relative to Sidekiq. Treat it as non-adoptable and low-effort-to-replace unless you are already a Symfony shop that clears the PHP version gate.
- What are the best alternatives to mcfedr/resque-bundle for Laravel?
- For a Laravel application, Laravel's native Redis queue with Horizon is the first-class answer: it covers the same Redis-backed worker use case with built-in observability, retries, and supervision guidance. If you specifically need Resque interop, use php-resque or a maintained fork directly behind a service provider. If you need to talk to existing Ruby Resque consumers and resque-web dashboards, integrate at the JSON payload level instead of adopting a Symfony bundle.