Repository navigation
STE-54: production runs on a VPS at api.sterish.xyz - #59
Merged
Merged
Conversation
…ish.xyz in the tunnel ingress Production ran on Proxmox pve02 CT 204, which went down when the node was rebuilt, depends on home power and internet, and had no IPv6 route. Cutover 13:49:02-13:49:16 UTC, ordered so two ledgers never both take payments: API stopped on the old host, payments ledger copied with the same sha256 on both sides (8 settlements, 0 owed), VPS API and tunnel connector started, old connector stopped. The tunnel now has one connector, origin 187.53.142.100. Verified through the public hostname on the VPS: verify.sh all pass; a real purchase (settle, mint, SEP-53 proof, six refusal cases, second payment not charged); 9 ledger rows (8 migrated + 1 new); API log shows real visitors, 0 5xx, 0 warnings (the IPv6 RPC retries are gone). deploy/cloudflared-config.yml gains api.sterish.xyz as the canonical hostname and keeps api-sterish.jameshub.fun. Its DNS record still has to be created: the origin cert on hand is scoped to jameshub.fun, and route dns with it created a stray api.sterish.xyz.jameshub.fun instead, to be deleted. Until then REPORT_BASE_URL stays on the old hostname.
…ranscript regenerated through it The CNAME was added in the sterish.xyz zone from the dashboard and the stray api.sterish.xyz.jameshub.fun record created by the zone-scoped origin cert was deleted. REPORT_BASE_URL now points at api.sterish.xyz. verify.sh passes through the new hostname, every URL the API builds uses it, the old hostname still answers, and the D3 transcript is 15/15 through it.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Linear: STE-54 · reviewers @axelmatsama @fable
Docs and deploy config only. The migration itself was done and verified on 17 September; this PR is its record.
What changed operationally
187.53.142.100(Ubuntu 26.04, 2 vCPU / 8 GB, IPv4 + IPv6), and is served athttps://api.sterish.xyz.api-sterish.jameshub.funis kept as an alias.sha256on both sides, 8 settlements, 0 owed), VPS started, old connector stopped.*.DISABLED-moved-to-vps.Verified through the public hostname
deploy/verify.sh: all pass.api.sterish.xyz: 15/15.Files
deploy/cloudflared-config.yml(addsapi.sterish.xyz),deploy/README.md(where production runs),docs/deployments.md(migration record),docs/evidence/ste-54-vps-migration-2026-09-17.json.Note on process
Merged on James's instruction rather than waiting for ACC: the change is already live and verified, and the PR had been open for review for 7 days. @axelmatsama, review after the fact and say if anything should be adjusted.