- How do I install tanwencn/supervisor in a Laravel application?
- Run composer require tanwencn/supervisor, then let Laravel package auto-discovery register the service provider, and publish the package config with php artisan vendor:publish. You then call the package facade or helper from your job or command code to emit behavior records. Before committing, pin the exact version and confirm the composer.json Laravel and PHP constraints match your application, because the package has only one release from August 2021.
- Does tanwencn/supervisor actually control Supervisor processes, like start, stop, or restart?
- No. Despite the name, the package does not wrap supervisorctl or Supervisor's XML-RPC API and provides no process lifecycle management. It is a small logging and emit helper whose purpose is to conveniently output behavior records you want to monitor, which Supervisor then captures from the worker's output. Process supervision itself still comes from your supervisor.conf program definitions.
- Which Laravel and PHP versions does tanwencn/supervisor support?
- The README and release history do not state a clear compatibility matrix, and the last release was 2021-08-20, so the realistic ceiling is Laravel 8 with PHP 7.4 to 8.0. PHP 8.1 deprecations and Laravel 9, 10, or 11 breaking changes are unverified. Test it in a scratch Laravel skeleton on your exact PHP minor before adopting, and treat any framework incompatibility as a hard stop rather than patching around it.
- Is tanwencn/supervisor still maintained?
- No, it is effectively abandoned: roughly ten stars, a single maintainer, one tagged release in 2021, and no visible issue triage or security disclosure path. Code quality cannot be assumed because there is no visible test suite or CI. The MIT license is the one clear positive, so forking and owning the code yourself is legally unencumbered if you decide the functionality is worth keeping.
- How is tanwencn/supervisor different from Laravel Horizon or Telescope?
- Horizon is a full Redis queue dashboard and worker supervisor with metrics, balancing, and restart controls; Telescope is a local debugging assistant for requests, jobs, and queries. tanwencn/supervisor only emits structured records about behaviors you choose to report, with no dashboard and no process control. If your application already runs Horizon, Telescope, or an APM pipeline, this package is redundant and should be rejected on overlap grounds alone.
- Where does tanwencn/supervisor write its output: stdout, a Monolog channel, or a database?
- The documentation is thin and non-English, so the exact sink and schema must be confirmed by reading the vendor source before adoption. Realistically the package is a small layer over Monolog, meaning output lands wherever your configured channel sends it, and Supervisor captures stdout only if you point it there. Confirm the emitted fields as well, because job payload data may include PII that you do not want in worker logs.
- Is tanwencn/supervisor safe to use in production queue workers?
- Treat it as high risk. It sits in the worker boot path, so a package-level failure can stop queue processing entirely rather than merely losing a log line, and there is no security disclosure path or test coverage behind it. The safest pattern is to wrap every call behind a thin internal interface such as WorkerEventReporter, so the vendor package appears in exactly one adapter class and removal is a one-file change.
- Can I use tanwencn/supervisor with Laravel Octane or long-running workers?
- This is unverified and should be tested explicitly. Determine whether the package holds any state across jobs or requests, because leaked state is a real hazard under Octane and persistent queue workers. Boot an Octane worker and a standard queue worker in a scratch environment, run several jobs, and check for stale context, deprecation notices, and conflicts with your existing Monolog channel configuration.
- Does tanwencn/supervisor have tests or CI, and how should I test my integration?
- There is no visible test suite, CI configuration, or meaningful version tagging beyond the single 2021 release, so you must supply your own verification. Install it in a scratch Laravel skeleton on your target PHP minor, boot a worker, and assert that the expected records are emitted in the expected schema to the expected sink. Also confirm there are no provider conflicts and no deprecation notices before rolling it into an application.
- What are better alternatives to tanwencn/supervisor for monitoring Laravel queue workers?
- For Redis queues, Laravel Horizon covers worker supervision, metrics, and failure handling out of the box. For structured worker observability without a new dependency, a 30 to 50 line Monolog channel or a small custom reporter gives you the same emitted records with full control of the schema. Telescope, Sentry, Datadog, or New Relic cover deeper tracing, and any of these is a safer long-term bet than an unmaintained package in the boot path.