- What does indydevguy/supervisor do in a Laravel application?
- indydevguy/supervisor is a Laravel package that wraps Supervisor worker management so you can control queue worker processes from your application. It ships a publishable configuration file plus Artisan commands to start, stop, and monitor workers. It suits teams that want a code-driven alternative to hand-editing supervisorctl configuration.
- How do I install indydevguy/supervisor with Composer?
- Install it with composer require indydevguy/supervisor. Laravel package auto-discovery should register the service provider, so a manual provider entry is usually unnecessary. After installing, publish the config file and review the defaults before starting any workers. Check the README for the exact Laravel version constraints.
- How do I publish the Supervisor configuration file?
- Run php artisan vendor:publish and choose the indydevguy/supervisor provider or tag to copy the config into your config directory. The published file is where you define program names, queues, connections, process counts, and log paths. Commit it to version control so every environment deploys the same worker setup.
- Which Artisan commands does the package provide for queue workers?
- The package exposes Artisan commands that start, stop, and monitor queue workers managed through Supervisor. This lets you trigger worker lifecycle actions from application code, deploy scripts, or CI instead of SSHing into each server. Refer to the README for the exact command signatures and supported options.
- Do I still need Supervisor installed on the server?
- Yes. The package manages Supervisor programs and worker processes, but it does not replace the Supervisor daemon itself. You still need Supervisor installed and running on the host, typically through your system package manager. The package handles configuration and command orchestration around that daemon.
- Can I use this package to monitor worker status?
- Yes, monitoring is part of the package's scope, with commands that report whether workers are running. That makes it easy to sanity-check processes after a deploy or restart. For long-term observability, pair the status checks with your existing logging and alerting stack.
- How do I configure queues and the number of worker processes?
- Worker definitions live in the published config file, where you set the queue connection, queue names, process count, and restart behaviour. Tune the process count to match your queue throughput, and keep memory limits in mind for long-running workers. After editing, restart the workers so Supervisor picks up the changes.
- Does it work alongside Laravel Horizon, or should I choose one?
- Horizon provides its own process management and dashboard for Redis queues, so running both for the same queues is usually redundant. Choose this package when you want explicit Supervisor program files and Artisan-triggered control rather than Horizon's auto-balancing. Non-Redis drivers such as database queues are a natural fit.
- Is this package safe to use in production?
- It can be used in production, but treat it as a convenience layer on top of a correctly configured Supervisor daemon. Make sure workers run as the right system user, logs are rotated, and the daemon starts on boot. Exercise your start, stop, and monitor commands in staging before relying on them during an incident.
- How is the package maintained and which Laravel versions are supported?
- Pin the package to a compatible version in composer.json and review its changelog before upgrading, especially across Laravel major releases. Supervisor configuration formats are stable, so upgrades are typically low risk. If the package ever stalls, the config it publishes can be maintained manually.