- What is glit/resque used for in a Laravel application?
- It is positioned as a Laravel integration for Resque, a Redis-backed background job system for dispatching jobs, running worker processes, and configuring queues and job classes. In practice, the repository is a PHP Resque port with a pluggable job-instantiation delegate, not a framework-native queue replacement. Use it only if you specifically need Resque semantics and accept that the Laravel integration claims need verification.
- Does glit/resque support Laravel 10 or Laravel 11?
- The provided assessment does not confirm modern Laravel support; the lineage is likely PHP 5.6 to 7.x and Symfony 2.x/3.x era. The package description claims Laravel integration, but you should spike Composer constraints, the service provider, and Artisan commands on your target Laravel version. Expect deprecation issues on PHP 8.1+ and avoid assuming compatibility without a test.
- How do I install glit/resque with Composer?
- Mechanically it is Composer install plus a Redis connection, a worker entrypoint script, and job classes implementing a perform method. Because the package has zero stars and zero dependents, with abandonment risk, pin it by commit hash from a vendored or private mirror rather than floating a caret constraint. Verify the declared PHP and extension requirements and that pcntl and posix are available where workers run.
- Why does glit/resque need pcntl and posix?
- Resque-style workers fork child processes, so pcntl and posix are required. They are unavailable on Windows and are often disabled in hardened FPM or base images. Treat this as a container image and platform approval issue; the worker is a supervisor or systemd-managed daemon, not an Artisan command.
- Can I use Laravel's service container with glit/resque jobs?
- The fork's differentiator is a pluggable job-instantiation delegate, so job objects can be resolved from a container instead of being new'd reflectively; the README cites Symfony2's DIC. Wiring it to Laravel's container is typically small, such as instantiate with the class name and arguments. Confirm the hook is stable and documented rather than reverse-engineering an undocumented interface.
- Does glit/resque support retries, delayed jobs, or scheduled queues?
- No native retry, delayed or scheduled jobs, uniqueness, rate limiting, or dead-letter queue are described, so those become your code. Resque semantics are at-least-once with a visibility gap: a popped job killed before being recorded as in-progress can be lost, and a crash mid-execution can strand a job in the in-progress registry without automatic requeue. Laravel's native Redis queue plus Horizon provides maintained retries, backoff, timeouts, and observability.
- How should I test glit/resque jobs?
- Unit-test job classes by invoking perform with JSON-serializable arguments, and integration-test dispatch plus worker behavior against a real Redis instance. Because the worker is a daemon, test the supervisor entrypoint and the failure and restart path, not just job code. Also verify that the claimed service provider and Artisan commands actually exist before building test infrastructure around them.
- Is glit/resque safe for production?
- Risk is high due to project health: zero stars, zero dependents, a bus factor of one, and no downstream users to surface bugs or triage CVEs. The abandoned low-traffic Packagist namespace is a supply-chain takeover candidate, so mirror or vendor it and pin by commit. Operationally you own a forking daemon, failure recovery, and all missing queue features; for most Laravel apps native queues are safer.
- What are alternatives to glit/resque for Laravel queues?
- Laravel's native queue with the Redis driver and queue:work is the default alternative, and Horizon adds observability and management. The assessment explicitly says glit/resque is a poor fit for Laravel because native queues deliver the same semantics with maintained code and first-class retries, backoff, and timeouts. Choose Resque only for legacy Resque worker compatibility.
- How is glit/resque maintained and should I trust its Laravel claims?
- The assessment flags documentation credibility: the description claims a Laravel service provider, publishable config, and worker commands, but the repository is a Resque port whose enhancement is a Symfony2-era DIC delegate. Treat those claims as aspirational until a spike proves the provider and Artisan commands exist. With no stars or dependents, pin and audit it, and plan an exit path.