Weave Code
Resque Laravel Package
resquebundle/resque
ResqueBundle provides Symfony integration for Redis-backed Resque background jobs, with services and console commands to enqueue tasks, start and manage workers, and monitor queues. It wraps the PHP Resque port and adds simple configuration for queues and worker lifecycle in Symfony projects.
ResqueBundle for Symfony 4+
Frequently asked questions about Resque
- What is ResqueBundle and can I use it in a Laravel application?
- ResqueBundle is a Symfony bundle that integrates php-resque with Symfony configuration and console commands for Redis-backed background jobs. It is not a native Laravel package, so Laravel teams usually evaluate php-resque directly or Laravel's own Redis queue workers. You can study its worker lifecycle patterns, but do not assume Laravel service providers or Artisan commands are included.
- Does ResqueBundle support Laravel 10 or 11?
- There is no stated Laravel 10 or 11 integration in the provided overview; the package is documented as Symfony integration for php-resque. Laravel compatibility would depend on using php-resque outside the bundle or writing your own Laravel wrapper. Confirm PHP 8 and Redis requirements before assuming it fits a Laravel 10 or 11 stack.
- What PHP version is required for ResqueBundle 5.0.3?
- Release 5.0.3 is described as PHP 8-only, so PHP 7 projects must pin an earlier compatible release or upgrade the runtime. The exact minimum PHP 8 minor version is not specified in the provided context, so check the package composer.json before upgrading. Validate extensions and Redis client compatibility in staging.
- How do I install ResqueBundle and configure Redis queues?
- Install it with Composer as resquebundle/resque and configure Redis connections plus named queues in Symfony configuration. The bundle provides services and console commands for enqueuing jobs and starting workers. In Laravel you would need equivalent php-resque configuration rather than the bundle's Symfony config, so plan for custom wiring.
- How does Redis authentication work in StartWorkerCommand?
- Version 5.0.3 adds authentication support to StartWorkerCommand, which helps with secured Redis deployments. The provided context does not confirm whether auth is optional or required or which exact config and environment keys control it. Test both authenticated and unauthenticated worker startup and document the required variables for every environment.
- What changed from ResqueBundle 5.0.2 to 5.0.3 and is it breaking?
- The 5.0.3 release adds PHP 8-only support and authenticated worker startup, both meaningful behavioral changes. Even though it is published as a patch, PHP 7 deployments will break if they upgrade without a runtime change. Treat it as a potentially breaking upgrade and review an upgrade guide if one exists.
- How do I start and manage Resque workers in production?
- The bundle provides console commands for starting and managing Resque workers, including StartWorkerCommand. Production deployments should run workers under a process supervisor and restart them deliberately during releases. In Laravel, you would typically wrap php-resque worker startup in a custom command or supervisor program rather than relying on Symfony console commands.
- What are the best alternatives to ResqueBundle for Laravel background jobs?
- Laravel's native Redis queue with Horizon or queue workers is usually the simplest alternative for Laravel applications. Using php-resque directly gives you Resque semantics without the Symfony bundle layer. Symfony Messenger is another option if you are in a Symfony codebase, and each choice changes monitoring and worker management.
- How should I test Resque worker startup and Redis auth before production?
- Validate the upgrade in a staging environment with the same PHP 8 runtime, Redis authentication, and worker deployment scripts as production. Test job dispatch and processing end to end, then restart workers through your controlled deployment process. Confirm rollback to the prior package version and prior worker configuration works before production rollout.
- Is ResqueBundle 5.0.3 actively maintained and safe for production?
- The release includes a community PR and two meaningful behavioral changes, so confirm maintainer review depth, test coverage, and documentation before production use. Worker startup failures may appear as queue backlog rather than immediate application errors, which raises operational risk. Assign an internal owner for Redis connectivity and worker lifecycle issues and monitor queue depth.
Weaver
How can I help you explore Laravel packages today?