Repository navigation
ops(fly): add HTTP health check on /health - #17
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…hine Fly Machines ignore the Dockerfile HEALTHCHECK, and a failing Fly service check only stops routing and fails deploys; it does not restart. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Adds a Fly HTTP service check on
/healthtofly.toml. Infrastructure only: no code paths change, and the VM size (shared-cpu-1x, 512 MB), region (syd) and scale-to-zero settings stay as they are.Check settings: GET
/health, every 30s, 5s timeout, 10s grace period. The comment infly.tomlexplains each value.Already deployed to production from this branch. Merge it so the next deploy from
mainkeeps the check.Verified on the live app
fly deployfinished cleanly, and the machine shows as healthy.servicecheck-00-http-8080is passing./health,/dashboardand/metricsall return 200.oom_killed=false, and the logs contain no OOM lines.Context
This started as a right-sizing review. Idle memory was about 145 MiB of the 459 MiB usable, about 104 MiB of it the uvicorn process. 512 MB was kept.
A failing Fly check does not restart the machine. It only stops routing traffic to it and fails
fly deploy. Crash and OOM recovery comes from the machine's restart policy. This PR also corrects the comment insrc/relay/main.pythat claimed a failed health check restarts the machine. That change is comment-only.🤖 Generated with Claude Code