714c2aed86
The deploy docs predated the GCP name-alignment and described infrastructure that no longer exists. Discovered during the v0.31.4 deploy. Corrections: - Project wiggleverse-rfc -> wiggleverse-ohm; VM rfc-app -> ohm-rfc-app; install path /opt/rfc-app -> /opt/ohm-rfc-app; system user + service rfc-app -> ohm-rfc-app; external IP 34.132.29.41 -> 136.116.40.66. - SSH is now IAP-only (direct port 22 times out): document --tunnel-through-iap on every gcloud compute ssh. - Meta repo wiggleverse/meta -> wiggleverse/ohm-content. - Two-remote reality: the VM's git origin is git.benstull.org/benstull/ rfc-app, a SEPARATE Gitea from the release one (git.wiggleverse.org) that does not auto-mirror — so a release must be pushed to the benstull remote before the VM can fetch it. The VM tracks a detached release TAG, not a branch. - Frontend-only changes are live once dist/ is rebuilt (nginx serves it directly); pip install only when requirements.txt changed. Docs-only; no version bump (cf. the docs-only commit after v0.31.3). The First-Time Deployment blocks keep the structural commands with a substitution note rather than unvalidated rewrites. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>