- What is pdffiller/laravel-queue-qless and what does it do?
- It is a Laravel queue driver that connects Laravel's queue system to Qless, a Redis-backed job queue. Instead of pushing jobs to database, SQS, or plain Redis queues, you can dispatch Laravel jobs and have Qless schedule and process them. It lets you keep Laravel's familiar dispatch and worker APIs while using Qless for job management.
- How do I install laravel-queue-qless with Composer?
- Install it with composer require pdffiller/laravel-queue-qless and let Laravel package discovery register the service provider. After installing, publish any package configuration so you can register the Qless connection in your queue config. Confirm the resolved illuminate/support and PHP constraints in composer.json before rolling it out to an existing application.
- How do I configure the Qless queue driver in Laravel?
- Add a queue connection that uses the qless driver in config/queue.php and point your default or per-job connection at it. The connection needs the Redis/Qless server details such as host, port, and database, which the package config exposes. Once configured, standard dispatch calls route jobs through Qless without changing your job classes.
- Does laravel-queue-qless support Laravel 13?
- Version 1.11.2 is described as a framework-compatibility patch that adds Laravel 13 support, with no functional changes. Because it is a patch-level release, verify in composer.json whether it supports a range such as Laravel 10 through 13 or tightens the constraint to 13 only. Run your test suite against both your current Laravel version and Laravel 13 before upgrading in production.
- What Laravel and PHP versions does laravel-queue-qless require?
- The exact constraints are defined in the package's composer.json and can change between releases. The 1.11.2 release specifically targets Laravel 13 compatibility, so inspect the resolved illuminate/* and PHP requirements after running composer update. If you are on an older Laravel version, check that the new release still resolves without forcing a framework upgrade.
- Do I need a running Redis server to use Qless with Laravel?
- Yes. Qless stores its job data in Redis, so a reachable Redis instance is required for the driver to enqueue and process work. Configure the Redis connection details in your queue configuration and make sure your workers can reach the same server. For local development you can run Redis alongside your application or use a container in your development stack.
- How do I dispatch a Laravel job to the Qless queue?
- Dispatch jobs exactly as you would with any other Laravel queue driver, using dispatch or the Queue facade with onConnection and onQueue. The package translates those calls into Qless job submissions, so delays and queue names map onto Qless scheduling. Your job classes should stay free of Qless-specific code so they remain portable to other drivers.
- How do I test Laravel jobs that run on the Qless queue driver?
- Use Laravel's Queue::fake and Bus::fake helpers to assert that jobs are dispatched without touching Redis or Qless. For integration coverage, run a real Redis instance in CI and execute a worker against a test queue to confirm jobs are picked up and completed. Keep a matrix so you test both your deployed Laravel version and Laravel 13 if you plan to upgrade.
- What are the alternatives to laravel-queue-qless for Redis-backed queues?
- Laravel ships with a built-in redis queue driver that covers most background job needs without extra dependencies. Horizon adds monitoring and configuration on top of the native Redis driver, while other packages offer similar Qless or Beanstalkd integrations. Choose this package only when you specifically need Qless features such as its job tracking and scheduling model.
- Is laravel-queue-qless safe for production and how actively is it maintained?
- The 1.11.2 release is a narrow compatibility patch tracking Laravel 13, which suggests the maintainer is following framework releases. Before adopting it, check the repository's release history, open issues, and CI test matrix for evidence against your Laravel and PHP versions. If the queue is business-critical, pin a tested version and keep a rollback path to the previous release.