Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Health endpoint GET /_/health for readiness checks

Open
#89 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
70/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
php
Domain
api, backend

Research direction

The health endpoint needs to be added to the routing in routing/all.php. Start by examining the existing API routes and the access control configuration. Implement a controller or handler that performs a dummy database select and returns the appropriate JSON response with the correct HTTP status codes and cache headers. Test the endpoint to ensure it works without authentication and is excluded from caching.

Written by the indexing model from the issue text.

Description

documentation

Source: components-web-app/api-components-bundle#312 (PR #315)

GET /_api/_/health (the /_/health route under the application's API prefix):

  • 200 {"status":"ok"} after a dummy select on the default database connection; 503 {"status":"unavailable","reason":"database"} otherwise.
  • Never cached (Cache-Control: no-store), no surrogate keys, no session; cheap enough to probe every few seconds. Use it for Docker/compose healthchecks and Kubernetes readiness probes, and exclude it from Souin's cache.
  • Imported through routing/all.php. An application whose access_control requires login for every GET must allow it: { path: ^/_api/_/health, roles: PUBLIC_ACCESS }.
  • Only the database is checked; optional services (Mercure, the cache) don't fail it.
Dominant language
Vue
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from components-web-app/docs

All issues in components-web-app/docs

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.