Repository navigation
fix(gateway): probe a site's health without needing curl in its image - #661
Merged
Merged
Conversation
The compose health check for a website backend ran curl, so a site image without curl could never turn healthy, even with its server answering. The probe now fetches with whichever of curl, wget, python3 or node the image has.
andrewpark-scaleai
enabled auto-merge (squash)
November 13, 2026 06:51
earakely-scale
approved these changes
Nov 13, 2026
andrewpark-scaleai
deleted the
andrew.park/website-probe-without-curl
branch
November 13, 2026 17:42
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
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.
Why
A website env whose server image doesn't contain
curlcan never deploy. The compose health check the gateway writes for a site's backend runscurl, so the check exits 127 and compose marks the service unhealthy. That happens even while the server is up and answering its card. Production hit this with a one-image site built from the Notes example minus itsapt-get install curlline. Every deploy failed after 90 to 120 s with "failed its health check", even though the captured log showed uvicorn running. Nothing told the author thatcurlwas required. The only mention was a line in the example's README.What
_http_probebuilds the backend health check. It tries the card and then the declared health path, using whichever ofcurl,wget,python3ornodethe image has, and passes on the first success. A server that answers only with errors still fails it.curl, and its README no longer says the gateway needs it.Verification
curl: not found).node:22-slim(node only) and busybox (wget only) when the server answers, and fails when the server answers 500 or nothing is listening.python3, against a server answering 200, and then against one answering only errors.env_gateway_provider_test.pypasses (270), and so do the Notes example tests.

Confidence Score: 5/5
The PR appears safe to merge.Summary
Website health checks now use the first available client among
curl,wget,python3, andnode.The latest change only removes extra whitespace between shell branches. No new issues were found, and the previous request-limit finding is fixed.
Reviews (3) · Last reviewed commit: "style(gateway): single spaces between th..." · Reviewed by Greptile