vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(corviduo-dev): Worldtree deploys (demo/pinned/personal) are CI/CD-only, not infra-ops

Browse Source 
worldtree-dev sent infra-ops a manual deploy request for v0.30.6 to
personal:8081; operator confirmed all three corviduo-dev Worldtree
deployments go through the Worldtree team's CI/CD, never a manual
infra-ops deploy. The old 'personal — manually managed' line was wrong
and misleading. docker-as-root pattern is emergency-ops (key restore)
only.
This commit is contained in:
Vuong Hoang
2026-06-03 13:46:05 -07:00
parent 9090fb59d7
commit d8d776c7a3
1 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
servers/corviduo-dev/README.md
+11 -2
View File
@@ -44,10 +44,19 @@ Three `docker compose` projects under `/opt/`:
| Project dir | Container name | Role |
|---|---|---|
| `/opt/worldtree/` | `worldtree-worldtree-api-1` (port 8080) | Demo deployment — auto-deployed by Worldtree's CI on every push to `main`. The "shared" Worldtree instance vor + asset-engine talk to. |
| `/opt/worldtree-personal/` | `worldtree-personal-worldtree-api-1` (port 8081) | Personal deployment — manually managed, separate compose project, persistent state independent of demo. |
| `/opt/worldtree/` | `worldtree-worldtree-api-1` (port 8080) | Demo deployment — the "shared" Worldtree instance vor + asset-engine talk to. |
| `/opt/worldtree-personal/` | `worldtree-personal-worldtree-api-1` (port 8081) | Personal deployment — separate compose project, persistent state independent of demo. |
| `/opt/worldtree-pinned/` | `worldtree-pinned-worldtree-api-1` (port 8082) | Pinned deployment — intentionally lags behind `demo` for regression/comparison purposes. |
> **Deploys are CI/CD-only — NOT an infra-ops job.** All three
> deployments (demo, pinned, personal) are deployed exclusively by the
> Worldtree team's CI/CD pipeline. infra-ops does **not** deploy these
> manually. A peer "deploy Worldtree vX.Y.Z to <deployment>" request
> sent to infra-ops is **misrouted** — point them back to their
> pipeline; do not run the docker-as-root pattern to do it. The
> docker-as-root pattern below is for **emergency-ops only**
> (provider-key restore), not routine deploys.
Each project has:
- `compose.yaml` (image, env wiring, healthcheck, port mapping)
- `.env` (provider keys, ports, image tag — `deploy:deploy mode 600`)