mirror of
https://github.com/hanzo-docs/docs.git
synced 2026-10-26 10:55:57 +00:00
zeekayandHanzo Dev
bdd873596f
Reverses my own deletion of api/{vms,containers,clusters}.mdx. I deleted them
because platform's dokploy root.ts registers no cluster/vm/container router and
the dotted tRPC form 404s. Both facts are true and the conclusion was still
wrong: those capabilities DO exist, in cloud's visor and platform apps, under
different names. Rewriting beats deleting when the surface is real.
Mapped to source, each probed 403 against a 404 bogus control:
vm.all -> GET /v1/machines visor.go:143
vm.one -> GET /v1/machines/{id} visor.go:149
vm.launch -> POST /v1/machines {name,size,region,dryRun} visor.go:148
vm.destroy -> DELETE /v1/machines/{id} visor.go:151
cluster.all -> GET /v1/clusters visor.go:184
cluster.one -> GET /v1/k8s/clusters/{id} visor.go:208
cluster.create -> POST /v1/k8s/clusters | POST /v1/clusters (BYO)
addNode/removeNode -> pool ops: POST /v1/clusters/{id}/pools[/{pool}/scale]
container.* -> /v1/platform/projects/{project}/apps... platform.go:230
Operations with no route are DELETED, not invented: vm start/stop/restart,
vm volumes, web terminal, cluster update/rename, per-cluster access grants.
The pages now say so instead of documenting them.
Two /api/ remain and both are correct: captable.mdx:159 describes the
SELF-HOSTED Next.js route handlers (and states the hosted service serves
neither), and platform api/index.mdx links doc-site routes (/docs/api/...),
which are directory names, not endpoints.
Nav restored for the three pages. Dangling meta.json entries: 15, vs 22 on
origin/main -- still a net improvement, none introduced.
Co-authored-by: Hanzo Dev <[email protected]>