Andras BacsaiandClaude Opus 5.5 aabd127374 fix(compose): keep content files inside the resource directory ...

- A Compose bind volume with a Coolify `content:` block could make
  Coolify write any host file (for example /root/.ssh/authorized_keys)
  when the file was loaded. Content sources must now be inside the
  resource directory (./ paths); other sources get a clear validation
  error for services and applications (UI, API, load, deployment),
  and every content write is confined again on the server. Bind
  mounts without content are unchanged. All 94 template content
  volumes use ./ paths and still work.
- Quote container names in scheduled tasks and in the stop actions for
  applications, previews, and services.
- Fix a development-only crash when a preview with a bind mount was
  parsed (the preview suffix returned a plain string).

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

2026-09-27 14:37:21 +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 content files inside the resource directory

2026-09-27 14:37:21 +02:00

app.php

…

getHelperVersion.php

…

getVersion.php

…

includeHelpers.php

…