Weave Code
Supervisor Bundle Laravel Package
helppc/supervisor-bundle
A Symfony bundle that integrates Supervisor process control into your application, letting you configure, manage, and monitor supervisord programs from a single place with minimal setup.
Manage your Supervisor instances from a Symfony application.
Frequently asked questions about Supervisor Bundle
- What is helppc/supervisor-bundle and is it a Laravel package?
- It is a Symfony bundle that integrates Supervisor process control, letting you define supervisord programs in configuration and manage their lifecycle via console commands. It is not a Laravel package: it relies on Symfony bundle registration, a DI extension, and a configuration tree that Laravel's container does not consume. For Laravel apps it is best treated as a build-vs-buy input rather than a drop-in dependency.
- Can I use helppc/supervisor-bundle in a Laravel application?
- Not directly. You would either depend on the bundle and instantiate its non-bundle service classes from a Laravel service provider, or vendor and port the XML-RPC client. Both paths add coupling to a package with zero ecosystem traction and a recent major-version break. A spike is reasonable, but production adoption is not recommended as-is.
- Does helppc/supervisor-bundle manage Laravel queue workers or Horizon?
- No. It is ops tooling for arbitrary Supervisor programs, not Laravel queue worker management. Laravel Horizon remains the right answer for Redis-backed queue workers, including balancing, metrics, and failure handling. This bundle's scope is broader process supervision and does not replace Horizon.
- Which Symfony and PHP versions does helppc/supervisor-bundle v2.0.0 require?
- Version 2.0.0 raises the runtime floor to PHP 8.2 and supports Symfony 6.4, 7, and 8. That is good hygiene but a compatibility cliff for anyone still on PHP 8.1. It also shows that minor-to-major jumps happen in this package, so pin the version if you fork or port it.
- What changed in helppc/supervisor-bundle v2.0.0?
- The material change is per-server authentication, which models credentials per configured Supervisor server and partially answers the biggest open question about auth. The release also adds hidden_processes filtering, a restart feature of ambiguous scope, and bumps PHP and Symfony constraints. It is a hard major-version break on a package that had little prior API stability. Confirm whether restart is a new API method, UI action, or fix before relying on it.
- How does authentication work with Supervisor's XML-RPC interface in this bundle?
- v2.0.0 adds per-server credentials, but you must verify whether that maps to standard HTTP basic auth against Supervisor's inet_http_server or to something custom. If it is real basic auth, your threat model improves from unauthenticated process execution to a single shared secret, still without transport security unless TLS is terminated in front. Unix sockets remain preferable to TCP even with auth.
- Is helppc/supervisor-bundle production-ready and well maintained?
- It has zero ecosystem traction and a single external contributor, so it is not community-maintained in any meaningful sense. The v2.0.0 release is attributable and PR-linked, which resolves earlier recency concerns, but the health signals remain unverified. Treat it as a build-vs-buy input and pin any fork before the next major lands.
- What are the alternatives to helppc/supervisor-bundle for Laravel process supervision?
- For Laravel queue workers, Horizon is the default answer, and Supervisor itself is still the standard process manager outside Laravel. If you need programmatic Supervisor control, a small XML-RPC client or a maintained Laravel-specific process package may be a better fit than porting a Symfony bundle. The bundle's opinionated hidden_processes filtering is logic you would likely diverge from anyway.
- How do I test a Laravel integration with helppc/supervisor-bundle?
- Start with a spike: install the bundle in a throwaway Symfony-compatible setup, instantiate its service classes from a Laravel provider, and exercise the XML-RPC client against a real or mocked supervisord endpoint. Verify per-server auth behavior against inet_http_server basic auth and test over a Unix socket where possible. Keep the spike isolated so you can compare the effort against writing a minimal client.
- Does helppc/supervisor-bundle support environment-aware configuration generation?
- Yes, the bundle advertises environment-aware Supervisor configuration generation, along with declarative program definitions, console commands to start, stop, restart, and inspect processes, and centralized logging and status checks. Those features are Symfony-oriented and assume bundle registration and DI extension conventions. In Laravel you would need to reimplement or bypass that wiring.
Weaver
How can I help you explore Laravel packages today?