v0.331.0: a removal deletes the volumes still labelled with the app's project that its definition no longer declares (R-1117)

compose down --volumes removes only the current definition's volumes; a volume a template dropped (or an older restore re-created) survived 'remove with data' on 9202 (nextcloud_nextcloud_redis_data). Red-proofed.
2026-10-18 22:42:52 +02:00
parent 772ef36f5f
commit 8ae9178138
6 changed files with 102 additions and 3 deletions
@@ -1055,7 +1055,7 @@ The `/apps/{slug}` page renders hero section, screenshots, setup guide, and opti
 | Stop | `docker compose stop` (blocked for protected stacks) |
 | Restart | `docker compose restart` |
 | Update | `docker compose pull` + `docker compose up -d` |
-| Remove | `docker compose down --volumes` + remove `app.yaml` + optional HDD/backup cleanup; template preserved for redeploy |
+| Remove | `docker compose down --volumes`, then every volume still labelled with the app's compose project (one a template dropped or an older restore re-created — v0.331.0, R-1117) + remove `app.yaml` + optional HDD/backup cleanup; template preserved for redeploy |
 | Delete | `docker compose down --rmi local --volumes` + optional HDD data cleanup (orphaned stacks only) |

 **Remove vs Delete**: "Eltávolítás" (Remove) is for deployed catalog stacks — it reverts the stack to "Nincs telepítve" state while keeping the template for easy redeployment. "Törlés" (Delete) is for orphaned stacks — it removes the entire stack directory including templates. Both require stopping the stack first.