- What is kamisama/php-resque-ex used for?
- kamisama/php-resque-ex is a PHP port of Resque that provides Redis-backed queueing and worker processes for asynchronous background jobs. It is an enhanced fork of php-resque with phpredis support and additional logging options. It is best suited to legacy or Resque-compatible systems rather than greenfield Laravel applications.
- Is kamisama/php-resque-ex a native Laravel queue driver?
- No, it is a standalone Resque-style worker and queue library, not a Laravel-native queue driver. Laravel applications would need a custom adapter or bridge between Laravel dispatch code and Resque payloads. It does not provide native Laravel queue events, Horizon integration, batching, chaining, or failed-job handling out of the box.
- How do I install kamisama/php-resque-ex with Composer?
- You would install it with Composer using the package name kamisama/php-resque-ex. Because the repository is archived, you should pin a specific version or fork it internally before relying on it in production. You will also need Redis and, if you want phpredis support, the ext-redis PHP extension available to producers and workers.
- Does kamisama/php-resque-ex support phpredis?
- Yes, the package advertises phpredis support in addition to its Resque-style Redis queueing model. For reliable production behavior, use phpredis consistently across both job producers and workers. You should validate the phpredis and Redis server versions against your target PHP runtime before committing.
- Can I use kamisama/php-resque-ex with Laravel Horizon?
- No, kamisama/php-resque-ex is not compatible with Laravel Horizon because it is not a Laravel queue driver. Horizon monitors Laravel's native Redis queue system through its own job payloads, events, and metrics. Using php-resque-ex means operating a separate worker runtime and observability stack alongside Laravel.
- What Laravel and PHP versions does kamisama/php-resque-ex support?
- The provided context does not specify exact Laravel or PHP version compatibility, so you must validate this against your target runtime. Check PHP version support, phpredis compatibility, Redis server version, and Laravel container bootstrap requirements before committing. Because the package is archived, you should not assume current Laravel or PHP releases are supported.
- Is kamisama/php-resque-ex still maintained?
- No, the repository is archived, which means there is no upstream security patching, dependency refresh, or support. With a small community around the package, you should treat it as a vendored or forked component with an internal owner. Production adoption requires a plan for patching and compatibility maintenance.
- How do I handle failed jobs and retries with php-resque-ex in Laravel?
- You must design retry semantics, failure handling, timeouts, and duplicate-execution behavior explicitly because php-resque-ex does not plug into Laravel's native failed-job system. Logging options can help, but you should map worker logs into your central Laravel logging and monitoring stack. Test failure paths carefully before relying on the queue for critical work.
- Can I run kamisama/php-resque-ex workers in Docker or under Supervisor?
- Yes, Resque-style workers are typically run as long-lived processes under Supervisor, systemd, or a container orchestrator. In Laravel environments, containerizing workers and scaling them independently is the safer integration pattern. You should also account for memory growth, stale code, orphan processes, and health checks in long-running PHP workers.
- What are alternatives to kamisama/php-resque-ex for Laravel background jobs?
- For most Laravel applications, the native Redis, database, or SQS queue drivers with Horizon and Supervisor are the better fit. They provide job dispatch, retries, failed-job handling, events, batching, chaining, and observability without a separate Resque runtime. Consider php-resque-ex only when Resque wire or payload compatibility is a hard requirement or an existing Resque system must interoperate.