fix(deploy): isolate compose smoke resources

2026-07-11 22:16:51 +02:00
parent 767df63a33
commit 0ca6346f75
3 changed files with 56 additions and 12 deletions
@@ -39,4 +39,8 @@ Run the end-to-end packaging check with:

 The smoke script validates Compose, builds and waits for both services, checks health through
 the frontend, verifies SSE response headers, restarts the core, and confirms `/data` survives.
-Its cleanup preserves the named volume.
+Each run uses a unique Compose project and removes that project's containers, network, and test
+volume afterward. It never targets the fixed `thothii` operator project or its volume. Set
+`SMOKE_PROJECT` to a different explicit project name for reproducible debugging, and set
+`KEEP_SMOKE_RESOURCES=1` to retain that smoke project's resources for inspection; remove them
+later with `docker compose --project-name "$SMOKE_PROJECT" --profile external down --volumes`.