- What is phppro/supervision used for in a Laravel application?
- phppro/supervision is a lightweight supervision and monitoring package aimed at Laravel applications. It lets you register health checks for database connectivity, cache, queue status, or external APIs and exposes structured results for JSON endpoints or dashboards. The assessment also notes framework-agnostic PHP usage, with the Laravel integration acting as a wrapper over a core runtime.
- How do I install phppro/supervision with Composer?
- Install it with Composer using composer require phppro/supervision. If the package supports Laravel package discovery, the service provider should be registered automatically; otherwise add the provider manually and publish any configuration file. Then define your checks and run the provided Artisan command to confirm the setup works.
- Does phppro/supervision replace Supervisor, systemd, or Laravel Horizon?
- Do not treat it as a drop-in replacement for Supervisor, systemd, or Laravel Horizon without reviewing the source. The package describes process supervision and restart-related capabilities, but it is unproven and has no visible production usage in the assessment. Running two supervisors over the same worker pool is a known outage pattern, so choose one owner for the process tree.
- How do I add a custom health check to phppro/supervision?
- The package advertises a pluggable health-check contract for custom probes. You typically implement that contract, return a structured success or failure result, and register the check through configuration or the service provider. Confirm the exact interface and registration API in the source or README before building on it.
- How do I run phppro/supervision checks with Artisan or on a schedule?
- The package includes Artisan commands for running checks manually or on a schedule. Add the command to Laravel's scheduler if you want periodic checks, and route the structured output to a JSON endpoint or dashboard. In production, make sure the scheduler is actually running and that check results are monitored.
- Which Laravel and PHP versions does phppro/supervision support?
- The provided package overview does not state the PHP floor or Laravel version constraints. Check the package's composer.json and CI configuration for enforced support ranges before adopting it. Because there is no visible release history in the assessment, verify compatibility against your Laravel version rather than assuming it.
- Where does phppro/supervision store health status, and does it phone home?
- The overview describes structured results but does not specify whether health state is held in memory, cache, logs, or an external service. Review the configuration and source for any outbound network calls, and disable telemetry by default if it exists. For production, prefer storing state where your existing monitoring can read it.
- Is phppro/supervision production-ready or actively maintained?
- The assessment shows no visible stars, dependents, tagged releases, or CI signal, so treat it as unproven. A supervisor bug can leave workers dead or trigger restart loops, which raises the review bar above a typical utility package. If you adopt it, pin a commit, review the source, and keep a fallback supervision layer.
- How does phppro/supervision handle failures, thresholds, and restarts?
- The overview mentions configurable thresholds and failure handling, but the exact restart policy, backoff, grace periods, and signal handling are not specified. Review the source to understand how aggressively it restarts workers and how it avoids thundering-herd behavior against a recovering database. Test failure scenarios in staging before relying on it in production.
- What are alternatives to phppro/supervision for Laravel monitoring and process supervision?
- Alternatives depend on what you are supervising: Supervisor and systemd for daemons, Laravel Horizon for queue workers, and Kubernetes or ECS health checks for orchestrated containers. Laravel Pulse, Telescope, and Sentry cover observability but not process restart. Use phppro/supervision only if it replaces an existing layer rather than duplicating one.