LXC 128 trmnl hosts the TRMNL plugins middleware (dtoro/terminalito), polled by TRMNL cloud. trmnl-plugins.service on :9851; Caddy block + LE cert; VPS traefik router trmnl-public + cert mirror. Public path pending VPS<->home netbird route recovery (was "No networks available" at provision time, artifacto/blog 504 too). LAN Technitium record + SOPS enrollment + Google/MVG creds pending. Plan -> In Progress. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
18 lines
958 B
Markdown
18 lines
958 B
Markdown
# Plans
|
|
|
|
Pre-flight runbooks for planned changes that haven't happened yet. Once executed, move the outcome to `investigations/` (if anything interesting happened) or just a changelog entry on the affected node pages.
|
|
|
|
## Index
|
|
|
|
| Date | Title | Status |
|
|
| ---- | ----- | ------ |
|
|
| 2026-06-24 | [TRMNL plugins LXC (128) + middleware deploy pipeline](2026-06-24-trmnl-plugins-lxc.md) | In Progress |
|
|
| 2026-06-01 | [Slate AX → SODOLA managed switch migration](2026-06-01-slate-ax-to-sodola-migration.md) | Done |
|
|
|
|
## Conventions
|
|
|
|
- File name: `YYYY-MM-DD-<slug>.md`. Use the *target* date if known, otherwise the planning date.
|
|
- Status: `Planned` → `In Progress` → `Done` (update index entry as it moves).
|
|
- When done: add a changelog entry on every affected node page, then update status to `Done` here. If things went sideways, open an investigation.
|
|
- Plans are append-only once execution starts — don't rewrite pre-flight intent after the fact.
|