Keep deployment logs findable after the container is recreated (closes #214)

Deployment logs were stored under a directory named after the container's hostname, and the path was worked out again from the current hostname on download. Docker gives a recreated container a new hostname, so every older log download returned 404. New logs now go to `logs/<appname>/` with no hostname in the path. Logs written by older versions under an old hostname directory are still found by looking one directory deeper, inside the same confined log root. Tests cover both the hostname-free path and downloading an old-layout log. Model: opus-5-5
2026-09-23 11:44:30 +02:00
parent 19619b1cd2
commit ddcd179841
4 changed files with 81 additions and 8 deletions
@@ -20,6 +20,10 @@ regress.

 # Completed Steps

+- 2026-09-23: Deployment log files are now stored under `logs/<appname>/`
+  instead of `logs/<hostname>/<appname>/`, so downloads keep working after the
+  upaas container is recreated; logs written under an old hostname directory are
+  still found (#214).
 - 2026-09-23: Fixed the flaky `t.TempDir` cleanup race in `internal/handlers`
  (the one fixed in `internal/service/webhook` by #198):
  `TestHandleWebhookProcessesValidWebhook` now waits with the webhook service's