Deploying on Coolify fails: volume interpolation mangled, slow on-server build, unreachable 127.0.0.1 bindings

[Bumpfi]

Prerequisites

• I searched open issues and this has not already been proposed.
• I searched discussions and this is not already being debated there.
• This is a concrete, actionable proposal — not a vague "it would be nice if..." request.

Area

Docker / Deployment

Problem or Motivation

Pointing Coolify v4 at docker-compose.yml fails for three separate reasons:

1. Volume interpolation mangled. Coolify's compose parser rewrites bind-mount sources and turns ${APP_DATA_DIR:-./data}/ssh:/app/.ssh:z (and the huggingface/local ones) into empty strings, so the deploy aborts with invalid spec: :/app/.ssh:z: empty section between colons.
2. Build from source on the server. The compose file uses build: ., so every deploy runs the full multi-stage build — 10+ minutes and enough RAM to OOM small VPSes — even though CI already publishes a multi-arch image to ghcr.io/pewdiepie-archdaemon/odysseus.
3. Unreachable / colliding ports. APP_BIND defaults to 127.0.0.1, which Coolify's Traefik proxy can't reach, and SearXNG claims host port 8080, which collides with other stacks on the same server.

Proposed Solution

Proposal: an opt-in docker-compose.coolify.yml (pre-built image, named volumes, no host ports, Coolify magic variables) plus a deploy guide, leaving docker-compose.yml untouched so existing setups are unaffected. PR: #5373

Alternatives Considered

No response

Prior Art / Related Issues

No response

Are you willing to implement this?

Yes — I can open a PR