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

Deployment log files were stored under a directory named after the container's hostname, which Docker changes whenever the container is recreated, so every older log download returned 404. Logs now live under logs/<appname>/. The download handler still finds logs written by older versions under any hostname directory. Model: opus-5-5
2026-09-23 09:08:50 +00:00
parent 19619b1cd2
commit 23649a7c60
4 changed files with 60 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