- Is jpvdw86/symfony-health-check-bundle compatible with Laravel?
- No. It is a Symfony bundle that depends on Symfony's bundle registration model, the Bundle base class, DI compiler passes, autoconfiguration tags, and a Symfony routing/event kernel. Laravel does not use FrameworkBundle or that lifecycle, so Composer may resolve the dependency but nothing will load. There is no Laravel service provider, facade, or publishable config surface.
- Can I install jpvdw86/symfony-health-check-bundle in Laravel with Composer?
- You can run composer require, but the package will not register routes or checks in Laravel. Laravel discovers packages through service providers, while this bundle expects bundles.php and Symfony kernel wiring. Without a custom adapter, installation produces no working health endpoint. Use a Laravel-native package or routes instead.
- What does jpvdw86/symfony-health-check-bundle do and what use cases does it cover?
- It adds health check endpoints to Symfony applications so you can monitor service availability and dependency status. Typical use cases are DB, cache, disk, and downstream service probes for operations dashboards, load balancers, or Kubernetes-style probes. It is small in scope by nature and is not a general monitoring platform.
- Does jpvdw86/symfony-health-check-bundle support Laravel 11 or Laravel 12?
- There is no evidence of Laravel 11 or Laravel 12 support. The November 2022 release most likely constrains PHP to around 8.0/8.1 and Symfony to 5.4/6.0, while Laravel 11/12 require PHP 8.2+ and Symfony 7 components. Treat it as untested and unsupported for modern Laravel.
- What are the best Laravel alternatives to this Symfony health check bundle?
- For Laravel, spatie/laravel-health is actively maintained and purpose-built for Laravel health checks. A native option is a small service provider with /health/live and /health/ready routes plus a check registry, usually around 150 lines. Define one JSON contract with status, checks, and duration, and return 200 healthy or 503 unhealthy so load balancers and probes parse consistently.
- Is jpvdw86/symfony-health-check-bundle safe to expose in production?
- High risk. Health endpoints are security-sensitive and often leak DB connectivity, version strings, and environment metadata on unauthenticated routes. This package has 1 star, 0 dependents, a single maintainer, and a 2022 release, so there is no downstream battle-testing or community CVE surfacing. Require auth or network restriction, split liveness and readiness, and get a maintenance sign-off before shipping.
- How do I configure jpvdw86/symfony-health-check-bundle in a Laravel app?
- In Symfony it is configured through bundles.php registration and bundle-level configuration. In Laravel there is no configuration surface because the bundle does not integrate: no service provider, no config publishing, and no route loading. If you need Laravel configuration, implement it in your own service provider and config file.
- Is jpvdw86/symfony-health-check-bundle maintained, and should I fork it for Laravel?
- Maintenance signals are weak: last release 2022-11-21, 1 star, 0 dependents, and one maintainer. Forking for Laravel is usually a bad trade because the adapter layer costs more than re-implementing the checks. Fork only for genuine Symfony services, with a pinned version, named owner, and compatibility sign-off; do not extend its footprint into Laravel.
- What PHP and Symfony versions does jpvdw86/symfony-health-check-bundle require?
- Based on the November 2022 release, expect PHP around 8.0/8.1 and Symfony 5.4/6.0, but verify composer.json constraints and transitive symfony/* requirements. Confirm those constraints admit your target Laravel version before any commitment. Modern Laravel 11/12 is likely outside that matrix.
- How do I test health check endpoints if I adopt this bundle?
- You cannot meaningfully test this bundle's endpoints inside Laravel because its routes and kernel wiring will not load. If you use it as reference, test your own Laravel health routes with feature tests that assert 200 for healthy and 503 for unhealthy, plus the exact JSON schema. Also test auth or network policy, dependency failures, and liveness versus readiness separation.