Weave Code
Ping Controller Laravel Package
libero/ping-controller
A lightweight Laravel package that provides a ready-made ping controller for health checks and uptime monitoring. Expose a simple endpoint to confirm your app is running and responding, without writing boilerplate routes—ideal for load balancers, monitoring services, and deployment checks.
Libero Ping Controller adds a ready-made health-check endpoint to your Laravel application, letting uptime monitors, load balancers, and container orchestrators confirm the app is alive with a single HTTP request. It ships a minimal controller and route wiring so you don't have to hand-roll a ping route in every project.
- Drop-in controller returning a lightweight ping response
- Configurable route path, middleware, and HTTP method
- JSON-friendly output for uptime and monitoring services
- Service provider registration following Laravel conventions
- No dependencies beyond the framework itself
Frequently asked questions about Ping Controller
- How do I install libero/ping-controller in a Laravel application?
- Install it with Composer by running composer require libero/ping-controller from your project root. Laravel's package auto-discovery should register the service provider automatically, but if it does not, add the provider to the providers array in config/app.php. The provided README excerpt is empty, so check the repository for any publishable config or migration steps before going further.
- What does the ping endpoint actually return?
- The package is described as a simple ping controller for health checks and uptime monitoring, so expect a minimal successful response confirming the application is responding. The exact status code, route path, and response body are not detailed in the available overview, so verify them against the source code or repository documentation. Most monitors only care that the endpoint returns HTTP 200.
- Which Laravel versions does libero/ping-controller support?
- The available context does not list a supported Laravel version range. Check the require section of the package's composer.json on Packagist to confirm compatibility with your framework and PHP versions. If you are on an older or very new Laravel release, test in a staging branch before rolling it out.
- Do I need to register the ping route manually?
- The package is intended to save you from writing custom routes and boilerplate, which implies the route is registered for you by the service provider. If the endpoint does not appear after installation, confirm package discovery is enabled or register the provider manually. The route path is not documented in the supplied excerpt, so check the package source to find exactly what URI it registers.
- Can I use this package for uptime monitoring with UptimeRobot, Pingdom, or Better Stack?
- Yes. Any external monitor that performs an HTTP request and checks for a 2xx response can point at the ping route this package exposes. Configure your monitor with the full URL, a short timeout, and a check interval that matches your alerting needs. Keep in mind that a simple ping only proves the app booted, not that the database or queue is healthy.
- How is this different from Laravel's built-in health check route?
- Laravel 11 and later ship with a built-in /up health endpoint, so this package is most useful when you want a dedicated controller from the Libero ecosystem or are working on a version without that route. It is deliberately lightweight, providing a single ping controller rather than a full diagnostics suite. If you need database, cache, or queue checks, pair it with a more complete health package.
- How do I write a feature test for the ping endpoint?
- Add a feature test that issues a GET request to whichever route the package registers and asserts a successful response, for example $this->get('/ping')->assertOk(). Once you confirm the exact URI from the package source, assert on the status code and any expected response content. This guards against future route or middleware changes silently breaking your uptime monitor.
- Can I customize the route path or the response returned by the ping controller?
- The overview does not describe configuration options, so there is no confirmed config file for changing the path or payload. If you need a different URI or response, extend or override the provided controller and register your own route that points to it. Check the repository for a published config before writing a subclass, since the package may already support it.
- Is it safe to expose a ping endpoint in production?
- A ping endpoint should return only a minimal confirmation and must never leak environment variables, stack traces, or version details, which is the intent of a lightweight controllers like this one. Leave debug mode off in production so any exception renders a generic error instead of a trace. If you want the endpoint hidden from the public internet, restrict it at the web server or middleware level and let your monitor authenticate.
- Is libero/ping-controller actively maintained, and what are the alternatives?
- The repository URL is unknown in the supplied context, so check Packagist for recent releases, download counts, and the latest commit date before adopting it. Alternatives include Laravel's built-in /up route, a hand-written route returning a JSON payload, or a broader package such as Spatie's laravel-health if you need dependency checks. For a single ping, the maintenance risk is low because the code surface is small and easy to replace.
Weaver
How can I help you explore Laravel packages today?