Andras BacsaiandClaude Opus 5.5 49ae227f6e fix(compose): keep the old volume of existing resources for external volumes ...

Switching an external volume from the old <uuid>_<name> volume to the
declared external volume on redeploy could make an app look as if it
lost its data (for example a database that initializes a new, empty
data directory).

- If a resource already has the storage entry with the old generated
  name, the parsers keep using that volume and show a warning in the
  deployment log and the service start log, with the steps to switch.
- Without that entry (new resources, or external volumes added later)
  the external volume is used as declared.
- Deleting the old storage entry (storage page) switches to the
  external volume on the next deployment; the storage entry shows a
  note about it.
- Legacy Compose applications (parser versions 1 and 2) never stored
  their volumes, so they keep the old volume names.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-27 17:24:51 +02:00

..

cache

fix(dev): support root bind mounts and LAN Vite access

2026-07-18 20:56:01 +02:00

helpers

fix(compose): keep the old volume of existing resources for external volumes

2026-09-27 17:24:51 +02:00

app.php

…

getHelperVersion.php

…

getVersion.php

…

includeHelpers.php

…