Repository navigation
Add GET /api/health for status.profullstack.com - #179
Merged
Merged
Conversation
/api/health fell through to the api [[...slug]] catch-all and returned the
JSON 404. The new route answers {status:ok, db:ok} with Cache-Control:
no-store after a select 1 through the shared client, or 503
{status:error, db:down} if the database does not answer within 3s.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan11 finding(s) MEDIUM: 9 | LOW: 2
Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a public
GET /api/healthso status.profullstack.com (Gatus) can check real app health instead of the home page.Why it 404'd: no route existed, so the path fell into
app/api/[[...slug]], which returns a JSON 404. A static segment wins over the optional catch-all.{"status":"ok","db":"ok"}afterselect 1via the existingsqlClient(libsql-pg over Postgres){"status":"error","db":"down"}on failure or after a 3s timeoutCache-Control: no-store, no auth, no error details, no new deps. The middleware only gates AI training crawlers and www->apex, so Gatus passes through.🤖 Generated with Claude Code