fix(infra): restore the region the service actually runs in - #255
Closed
aquie00t wants to merge 1 commit into
Closed
fix(infra): restore the region the service actually runs in#255aquie00t wants to merge 1 commit into
aquie00t wants to merge 1 commit into
Conversation
The previous change set `region: frankfurt` on a service running in Oregon. Render will not move a running service, and it does not ignore the line either - it fails the whole blueprint sync with "changing region not supported", so every other setting in the file stopped applying too, including the moderation variables added alongside it. The region is a description of where the service is, not a request to move it. Moving means creating a service in Frankfurt and pointing the domain at it; this line changes in that same piece of work. `plan: starter` stays, as that one is both true and something a sync can apply. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A2WFyQ3PR2jYvDVk89yZpc
Collaborator
Author
|
Superseded by the Frankfurt service export: the Oregon service it described has been replaced, so reverting its region is no longer the fix. |
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.
Summary
Sets
regionback tooregon, where the service actually runs.plan: starterstays.Root cause
#254 changed
regiontofrankfurtas a statement of intent. Its own deployment notes said the move requires recreating the service, because neither Render nor Neon relocates one — but the file was changed first anyway.Render does not treat an unreachable region as a no-op. It rejects the blueprint outright:
A rejected blueprint does not apply partially, so nothing else in the file synced either — including the
MODERATION_ENABLEDand Sightengine keys added for the media moderation work, andplan: starter.The mistake was ordering. This file describes the running service; it is not a request for a different one. The region line is the last step of a move, not the first.
What still needs doing
The measurement behind #254 stands: from Turkey, Frankfurt answers in 88 ms against 266 ms for Ohio and 287 ms for Oregon, Redis already runs in eu-central-1, and the community feed spends about a second crossing between them. The move is still worth making — it just cannot be made from here.
eu-central-1, dump and restore into it (1.5 MB), repointDATABASE_URL.starter, carry the environment across, moveapi.developernetwork.netto it.frankfurtin that same change, once it is true.Tests
Configuration only. Verified by reading the blueprint back after merge: the sync should succeed, and
plan: starterand the moderation variables should apply.AI asistan: Claude Opus 5