Skip to content

Document the Deploy stream as the VTA Farm and drop the "planned" placeholders - #38

Merged
geoffturk merged 1 commit into
mainfrom
document-deploy-stream-vtafarm
Sep 18, 2026
Merged

geoffturk merged 1 commit into
mainfrom
document-deploy-stream-vtafarm

Conversation

@geoffturk

Copy link
Copy Markdown
Contributor

Summary

The hardened Kubernetes deployment the sysop docs kept describing as "planned" or "not yet documented" now exists as three repos: vtafarm-k8s, vtafarm-api, and vtafarm. This PR updates every reference so the docs are current.

Changes

  • sysop/deploy/README.md is rewritten from a stub into an index page: what the VTA Farm is, which repo to read for what, the five OpenTofu layers vtafarm-k8s builds, prerequisites, and where the day-two runbooks live.
  • The deploy page maps each Explore walkthrough step to the Kubernetes Job the farm runs for it. The farm's full-stack mode automates the same offline sealed-bundle bootstrap: every setup --from <recipe> becomes a Job, every cross-directory file handoff becomes two PVCs mounted into one Job, and every nohup becomes a Deployment (see full-stack-setup-design.md). It also notes that a VTA Only session, which is what a developer's Personal VTA is, attaches to the farm's shared mediator and DID host and skips the bundle exchange.
  • sysop/README.md, the top-level README.md, the three explore pages, community-manager/README.md, and developer/01-personal-vta.md no longer describe the Deploy stream as planned or undocumented.
  • A VTA Farm row is added to the components table in the top-level README, and the CLAUDE.md layout table is updated.

Checks

  • markdownlint-cli2 "**/*.md" passes with 0 issues (run in Docker).
  • Every new GitHub link was checked and returns 200.

…ceholders

The hardened Kubernetes deployment the sysop docs kept describing as planned now exists as three ic3software repos: vtafarm-k8s (OpenTofu stacks for the Hetzner clusters and platform layer), vtafarm-api (the Go API that provisions per-user stacks), and vtafarm (the React frontend).

Rewrite sysop/deploy/README.md from a stub into an index page: what the farm is, which repo to read for what, the five OpenTofu layers, prerequisites, and where the runbooks live. It also maps each Explore walkthrough step to the Kubernetes Job the farm runs for it, since the farm's full-stack mode automates the same offline sealed-bundle bootstrap, and notes that a VTA Only session (a developer's Personal VTA) attaches to the farm's shared mediator and DID host instead.

Update every page that pointed at the Deploy stream as "not yet documented" or "planned": the top-level and sysop READMEs, the explore pages, the community-manager README, and the developer Personal VTA guide. Add a VTA Farm row to the components table and update CLAUDE.md's layout table.

Signed-off-by: Geoff Turk <geoff@ic3.dev>
@geoffturk
geoffturk merged commit df68ba1 into main Sep 18, 2026
2 checks passed
@geoffturk
geoffturk deleted the document-deploy-stream-vtafarm branch September 18, 2026 09:47
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