diff --git a/docs/servers.md b/docs/servers.md index 20f01ed8..d432970d 100644 --- a/docs/servers.md +++ b/docs/servers.md @@ -21,7 +21,8 @@ ssh br@deadpool-rezio-bridge # not implied ## Officer platforms -Eight, all running. **Verified 2026-08-27** — every row below was read off the machine, not recalled. +Six, all running. **Verified 2026-08-27**, minus the two Pertento hosts moved to "Deliberately skipped" on +2026-09-08 — every remaining row below was read off the machine, not recalled. | Host | Tailnet IP | Login | Port | Checkout | Domain | | ---------------------------- | ----------- | ----------------------------------------- | -------- | ----------------------------------- | --------------------------------- | @@ -30,8 +31,6 @@ Eight, all running. **Verified 2026-08-27** — every row below was read off the | `fofos` | 100.64.0.17 | `pastilhas` | 9000 | `~/officerdev/platform` | `officer.fofosfluffybastards.com` | | `macbookpro` | 100.64.0.9 | `pastilhas` | **9010** | `~/projects/officer-suite/platform` | `macbookpro.pastilhas.dev` | | `macbruno` | 100.64.0.22 | **`brunoalcadapadezmonteirodaconceicao`** | 9000 | `~/officerdev/platform` | — (none yet) | -| `production-pertento-bridge` | 100.64.0.12 | `pastilhas` | **9010** | `~/officerdev/platform` | `officer.pertento.ai` | -| `edge-pertento-bridge` | 100.64.0.15 | `pastilhas` | 9000 | `~/officerdev/platform` | `edge.pertento.ai` | | `deadpool-rezio-bridge` | 100.64.0.21 | **`br`** | 9000 | `/home/br/officerdev/platform` | `officer.rezio.dev` `[pending]` | **THE PORT IS NOT ALWAYS 9000.** Two hosts run on 9010 and it is in `OFFICERDEV_PORT` in each checkout's @@ -70,12 +69,21 @@ ssh host 'ls /opt/homebrew/bin/pm2 /usr/local/bin/pm2 ~/.nvm/versions/node/*/bin A host here is NOT a deploy target. A rollout names it as skipped and moves on — it is not a failure, and it must not be reported as one. -None today. `edge-pertento-bridge` was here from 2026-08-23 and came back up on 2026-08-24; it is a -deploy target again and its row is in the table above. +**Both Pertento hosts, since 2026-09-08** — `production-pertento-bridge` and `edge-pertento-bridge`. Owner's +call, not a fault found on either box. Details kept here rather than dropped, so putting them back is a +one-line move, not a re-derivation: -It was down long enough to matter, so expect it to be behind: when it returned it was 215 commits back at -`2026.08.22.02`, with no `roles` table and no commanders. A host coming off this list needs its schema -brought forward before it is treated as ordinary. +| Host | Tailnet IP | Login | Port | Checkout | Domain | +| ----------------------------- | ----------- | ------------ | -------- | ------------------------- | ----------------------- | +| `production-pertento-bridge` | 100.64.0.12 | `pastilhas` | **9010** | `~/officerdev/platform` | `officer.pertento.ai` | +| `edge-pertento-bridge` | 100.64.0.15 | `pastilhas` | 9000 | `~/officerdev/platform` | `edge.pertento.ai` | + +`edge-pertento-bridge` was skipped once before, from 2026-08-23 to 2026-08-24 — but that was downtime, not +a choice, and it came back as a deploy target. This is a different reason and there is no return date. + +It was down long enough to matter last time, so expect it to be behind whenever it returns: when it came +back on 2026-08-24 it was 215 commits back at `2026.08.22.02`, with no `roles` table and no commanders. A +host coming off this list needs its schema brought forward before it is treated as ordinary. On 2026-08-23 the deploy agent spent four attempts and up to 60s per try on this host before reporting it unreachable — TCP on 22 accepted, then no SSH banner. That work was correct and entirely wasted, which