Skip to content

STE-54: production runs on a VPS at api.sterish.xyz - #59

Merged
Lin1er merged 2 commits into
mainfrom
ops/54-vps-migration
Sep 24, 2026
Merged

Lin1er merged 2 commits into
mainfrom
ops/54-vps-migration

Conversation

@Lin1er

@Lin1er Lin1er commented Sep 24, 2026

Copy link
Copy Markdown
Owner

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

  • Production moved from the homelab LXC (Proxmox pve02, CT 204) to a VPS, 187.53.142.100 (Ubuntu 26.04, 2 vCPU / 8 GB, IPv4 + IPv6), and is served at https://api.sterish.xyz. api-sterish.jameshub.fun is kept as an alias.
  • Same Cloudflare Tunnel, now with the VPS as its only connector. Caddy listens on loopback, so the VPS exposes no HTTP port.
  • Cutover took 14 s, ordered so two copies of the payments ledger never both accept payments: API stopped on the old host, ledger copied (same sha256 on both sides, 8 settlements, 0 owed), VPS started, old connector stopped.
  • The old CT is stopped and kept for rollback, with its redeploy scripts renamed *.DISABLED-moved-to-vps.

Verified through the public hostname

  • deploy/verify.sh: all pass.
  • Real purchase e2e: paid exactly 0.1 USDC, SEP-53 ownership proof served, six refusal cases all 401, second payment settled nothing.
  • D3 transcript regenerated through api.sterish.xyz: 15/15.
  • Ledger continuity: 9 rows = 8 migrated + 1 new. As of 24 Sep: 10 settlements, all minted, and the VPS has been up 6 days.

Files

deploy/cloudflared-config.yml (adds api.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.

…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.
@vercel

vercel Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sterish Ready Ready Preview Sep 24, 2026 10:46am UTC

@Lin1er
Lin1er merged commit f83f855 into main Sep 24, 2026
3 checks passed

This branch was successfully deployed

1 active deployment
Preview — 9bf2feef Deployed Sep 24, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant