VersionControl:PRs/maybelle-config/263: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
cryptograss/maybelle-config#263, as GitHub has it |
cryptograss/maybelle-config#263, as GitHub has it |
||
| Line 16: | Line 16: | ||
|deploy=redeploy hunter | |deploy=redeploy hunter | ||
}} | }} | ||
<pre class="pr-body">Justin, #emergence, 16:42Z: retire `justin-arthel` along with `rj`, `skyler` and `fibonacci`. | |||
**What it does** | |||
- **Four containers retired:** `justin`, `rj`, `skyler` and `fibonacci` go into `retired:`. The playbook stops them and renames their compose files, and their homes stay on hunter's disk. Their `people:` entries (keys, names) stay too. | |||
- **My home moves to its own path.** `emergent-magent` gets `home_moved_from: /opt/magenta/justin/home`. A new task renames that directory to `/opt/magenta/emergent-magent/home`. It runs once, only after `justin`'s compose file has been retired, and never on top of a home that's already there. It's the same disk, so the 11G moves instantly, and every session resumes, because the mount point inside the container (`/home/magent`) doesn't change. | |||
- **The identity workaround goes.** `emergent-magent` now writes its own `.gitconfig`, so I commit as `magent-cryptograss`. The `home_dir` mechanism and its seven `when:` gates are removed, along with #260's `GIT_*` compose block. #262 is closed: it carried those variables through `su -`, and they're no longer needed. | |||
- **Routing:** `ssh sshrouter@hunter justin` (or rj, skyler, fibonacci) lands in `workbench`. The router already sent anyone without a container of their own there. Two router tests are updated to match. | |||
- **Firewall:** ufw closes the retired containers' ports, 2222–2224 and 14000–14029. Dropping them from a loop wouldn't remove rules that already exist, so a `delete: true` task removes them, once. | |||
- **Docs and the rest:** the recovery notes' paths to my memory, the router's usage comment, the log viewer's pane 0 (now the poller log in `emergent-magent`), the deploy summary and `CONTAINERS.md`. | |||
**What the deploy does, in order:** it retires the four containers, so `justin-arthel` stops. Then it moves the home while `emergent-magent` is still running; its bind mount follows the moved directory. Then it rewrites `emergent-magent`'s compose file with the new path and recreates it. Expect a minute or two of silence from me. | |||
**Checked:** hunter's 64 tests pass, including the router's 6. The four changed YAML files parse. Ansible isn't installed in my container, so I can't run `render-diff` locally; CI runs it. | |||
**Left alone:** `workbench`'s `people:` list, and deleting any home. That's a separate decision. | |||
Deploy: redeploy hunter | |||
Worked on by: magent, Justin, re, in #emergence</pre> | |||
Latest revision as of 17:06, 9 November 2026
| State | 🟣 merged 2026-11-01 17:17:05 |
|---|---|
| Worked on by | magent, justin, re |
| Moods | #emergence |
| Deploy | redeploy hunter |
| Branch | retire-personal-containers → production, by magent-cryptograss
|
| Opened · last pushed | 2026-11-01 16:45:49 · 2026-11-01 16:45:45 |
Justin, #emergence, 16:42Z: retire `justin-arthel` along with `rj`, `skyler` and `fibonacci`. **What it does** - **Four containers retired:** `justin`, `rj`, `skyler` and `fibonacci` go into `retired:`. The playbook stops them and renames their compose files, and their homes stay on hunter's disk. Their `people:` entries (keys, names) stay too. - **My home moves to its own path.** `emergent-magent` gets `home_moved_from: /opt/magenta/justin/home`. A new task renames that directory to `/opt/magenta/emergent-magent/home`. It runs once, only after `justin`'s compose file has been retired, and never on top of a home that's already there. It's the same disk, so the 11G moves instantly, and every session resumes, because the mount point inside the container (`/home/magent`) doesn't change. - **The identity workaround goes.** `emergent-magent` now writes its own `.gitconfig`, so I commit as `magent-cryptograss`. The `home_dir` mechanism and its seven `when:` gates are removed, along with #260's `GIT_*` compose block. #262 is closed: it carried those variables through `su -`, and they're no longer needed. - **Routing:** `ssh sshrouter@hunter justin` (or rj, skyler, fibonacci) lands in `workbench`. The router already sent anyone without a container of their own there. Two router tests are updated to match. - **Firewall:** ufw closes the retired containers' ports, 2222–2224 and 14000–14029. Dropping them from a loop wouldn't remove rules that already exist, so a `delete: true` task removes them, once. - **Docs and the rest:** the recovery notes' paths to my memory, the router's usage comment, the log viewer's pane 0 (now the poller log in `emergent-magent`), the deploy summary and `CONTAINERS.md`. **What the deploy does, in order:** it retires the four containers, so `justin-arthel` stops. Then it moves the home while `emergent-magent` is still running; its bind mount follows the moved directory. Then it rewrites `emergent-magent`'s compose file with the new path and recreates it. Expect a minute or two of silence from me. **Checked:** hunter's 64 tests pass, including the router's 6. The four changed YAML files parse. Ansible isn't installed in my container, so I can't run `render-diff` locally; CI runs it. **Left alone:** `workbench`'s `people:` list, and deleting any home. That's a separate decision. Deploy: redeploy hunter Worked on by: magent, Justin, re, in #emergence