Weave Code
Laravel Queue Ensurer Laravel Package
webparking/laravel-queue-ensurer
Keeps Laravel queue workers alive by monitoring your queues and automatically restarting stalled or missing workers, so background jobs keep processing without manual intervention or custom health checks.
This package provides a solid way to ensure all your required queues are running.
Frequently asked questions about Laravel Queue Ensurer
- What does webparking/laravel-queue-ensurer actually do?
- It monitors your Laravel queues and automatically restarts workers that have stalled or gone missing, so background jobs keep processing without manual intervention. Instead of writing custom health checks or waiting for someone to notice a dead worker, you get a package dedicated to ensuring all your required queues are running. It is a runtime dependency, not a dev-only tool.
- How do I install webparking/laravel-queue-ensurer?
- Install it with Composer using composer require webparking/laravel-queue-ensurer. It follows standard Laravel package conventions, so the service provider is registered via auto-discovery and you can publish the config file with php artisan vendor:publish. Pin to 1.3.* rather than a floating constraint if you want predictable upgrades.
- Does this package support Laravel 8?
- Yes. Version 1.3.0 widened the illuminate/* constraint to include ^8.0, which is what allows Composer to resolve the package inside a Laravel 8 application. Because 1.3.0 is a minor bump, it should be a no-op upgrade for existing 1.2.x consumers. Keep in mind that Laravel 8 is past end of life for security fixes, so factor that into your platform planning.
- Which Laravel and PHP versions are supported?
- The 1.3.0 release specifically adds Laravel 8 support, and the widened constraint implies compatibility with newer Laravel majors is retained as well. The exact PHP floor and the full supported matrix are not spelled out in the release notes, so check the package's composer.json before committing. Verify three layers: the PHP version floor, the illuminate/* constraint, and shared symfony/* transitive dependencies.
- How does the package know a queue worker has stalled or is missing?
- The package monitors your configured queues and restarts workers when it detects that a required queue has no active worker or that processing has stalled. The exact mechanics depend on the package's internal checks and how you configure which queues are required. Review the published config file after installation to see which queues it watches and at what interval.
- Is any configuration required after installation?
- You should publish the config file and define which queues must be running, since the package's core job is to ensure all your required queues are available. Auto-discovery handles service provider registration, so manual registration is typically unnecessary. Remember that config changes only take effect after clearing cached config in production.
- Can I use this in production, and does it replace Supervisor or Horizon?
- It is designed as a production runtime safeguard, but it complements rather than replaces process supervisors like Supervisor or Laravel Horizon. Supervisor keeps workers alive at the OS level, while this package focuses on ensuring the queues you require actually have running workers. Many teams run both, using the package as a second layer of protection.
- How do I test that queue ensuring works in my application?
- Trial-install 1.3.0 in a non-production branch and run your application test suite to confirm there are no dependency conflicts. Then simulate a dead worker in staging, for example by killing a worker process, and confirm the package restarts it. Review the composer.lock diff during the upgrade, since unintended dependency movement surfaces there.
- Does it work with Redis, database, and SQS queue connections?
- The package operates at the queue level in Laravel, so it applies to whichever connections your required queues are configured against, such as Redis, database, or SQS. Worker restart behavior depends on how your application launches workers, so validate against your actual connection and deployment setup. Check the config to ensure the queue names and connections you care about are covered.
- Is webparking/laravel-queue-ensurer actively maintained, and what are the alternatives?
- Version 1.3.0 adding Laravel 8 support shows the maintainer is still carrying the project, though a single-line changelog makes the long-term roadmap hard to judge. Alternatives include Laravel Horizon for Redis-backed queues, Supervisor for OS-level process management, and custom health-check scripts. If you already run Laravel 9 or newer, evaluate whether this release offers anything beyond what you already have.
Weaver
How can I help you explore Laravel packages today?