Retire lyra's SWAG dependency after app cutovers stabilise #36

Open
opened 2026-07-01 18:55:25 +01:00 by nimmo · 0 comments
Owner

Goal

Reduce or remove the SWAG Docker reverse-proxy dependency on lyra once enough application services have been migrated to stable host-native targets.

Acceptance Checklist

  • Inventory which public or LAN-facing services still depend on SWAG.
  • Decide which services should instead be targeted directly by Pangolin or another repo-managed ingress path.
  • Retarget at least the already-migrated native services away from Docker-network-only ingress.
  • Archive or remove the SWAG stack only after all dependent routes have been rehomed.

Context

The firewall comments in hosts/lyra/default.nix show that several web UIs are still reached through SWAG over Docker networks. That is workable during the migration, but it is not the intended end state if the underlying apps become native services.

Guardrails

  • Do not remove SWAG first and strand still-Dockerised apps.
  • Treat this as a late-stage cleanup item, not the opening move.
## Goal Reduce or remove the SWAG Docker reverse-proxy dependency on `lyra` once enough application services have been migrated to stable host-native targets. ## Acceptance Checklist - Inventory which public or LAN-facing services still depend on SWAG. - Decide which services should instead be targeted directly by Pangolin or another repo-managed ingress path. - Retarget at least the already-migrated native services away from Docker-network-only ingress. - Archive or remove the SWAG stack only after all dependent routes have been rehomed. ## Context The firewall comments in `hosts/lyra/default.nix` show that several web UIs are still reached through SWAG over Docker networks. That is workable during the migration, but it is not the intended end state if the underlying apps become native services. ## Guardrails - Do not remove SWAG first and strand still-Dockerised apps. - Treat this as a late-stage cleanup item, not the opening move.
Sign in to join this conversation.
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
nimmo/nixos-config#36
No description provided.