Per ADR-009: the tunnel origin is only as available as the machine running it, so barback.pezza.dev does not go live until the stack moves off the MacBook to the always-on Fedora PC. Timeline: a couple of months out (as of 2026-08). This issue gates #1 and #2 going live.
- This is ADR-005's restore drill executed for real:
bar:full-backup + copy of the bar_data and meili_data volumes onto the PC, docker compose up -d, re-run scripts/tag_families.py sanity check
- Move the tunnel token to the PC; verify the tunnel connects from the new host
- Docker on Fedora (daemon, not Desktop) so the stack survives logout/reboot via
restart: unless-stopped
- MacBook stays the dev machine talking to
localhost:8000, unaffected
- Post-migration validation (ADR-009): service worker registers and PWA installs from barback.pezza.dev off the LAN; anonymous requests stop at Access; data intact from backup
Per ADR-009: the tunnel origin is only as available as the machine running it, so barback.pezza.dev does not go live until the stack moves off the MacBook to the always-on Fedora PC. Timeline: a couple of months out (as of 2026-08). This issue gates #1 and #2 going live.
bar:full-backup+ copy of thebar_dataandmeili_datavolumes onto the PC,docker compose up -d, re-runscripts/tag_families.pysanity checkrestart: unless-stoppedlocalhost:8000, unaffected