Hotfix: turn the geo block off by default after it took the site down - #36
Merged
Merged
Conversation
Loading the city database cost about 179MB resident, which the production box could not carry alongside Postgres. Every database-backed route hung while /nope -- the only route touching no database -- kept answering, so the symptom read as a partial outage rather than a crash. - Gate the rule behind GEO_BLOCK_ENABLED=true, so a deploy no longer loads the database unless someone opts in - Leave the plug, the matching rules and their tests in place; the code is correct, it is the memory footprint that the host cannot take The 301 redirect work is unaffected and stays live. --- Pages affected: - [MCP Registry](https://ai.mcpharbor.dev/) — home page, restored by this change. - [Browse MCP servers](https://ai.mcpharbor.dev/servers) — the catalogue, restored by this change. - [JSON API](https://ai.mcpharbor.dev/api/v0/servers) — machine-readable listings. Co-Authored-By: Claude Opus 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
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.
Production outage after #35. Loading the DB-IP city database cost ~179MB resident, which the box could not carry alongside Postgres.
Symptom: every database-backed route hung (30s timeouts on
/,/servers,/submit,/llms.txt,/api/v0/servers), while/nope— the one route that touches no database — kept answering 301. The deploy's own smoke test passed at 16:38, becauselocusdownloads and decodes the database in the background after boot.Fix: the rule is now gated behind
GEO_BLOCK_ENABLED=true, so no deploy loads the database unless someone opts in. The plug, the matching rules and their tests stay — the code is correct; the footprint is what the host cannot take.The 301 redirect work from #32 is unaffected and stays live.
Re-enabling wants one of:
Pages affected:
🤖 Generated with Claude Code