-
fix(dokploy): keep cluster config across redeploys — relocatable runtime .env
Release / frontend (push) Canceled after 0sRelease / linux (amd64) (push) Canceled after 0sRelease / linux (arm64) (push) Canceled after 0sRelease / windows (push) Canceled after 0sRelease / macos (push) Canceled after 0sRelease / release (push) Canceled after 0sBuild and Push Docker Image / build-and-push (push) Canceled after 0sreleased this
2026-06-12 07:08:26 +03:00 | 225 commits to main since this releaseDokploy re-clones the compose project on every redeploy, so the
relative bind mounts in the dokploy compose variants (./.env:/app/.env,
./data/docker:/app/data) were wiped each time — the node lost RAFT_*,
the bridge secret and the Raft log, dropped out of its cluster and
stopped shipping to the uplink.- NODE_STATS_ENV_FILE relocates the runtime .env for both reads
(config.Load / godotenv) and writes (ConfigWriter — wizard, bridge,
auto-update toggle); the parent dir is created on first write; - both dokploy compose variants now keep ALL mutable state (.env,
SQLite DB, Raft log) in a named volume that survives redeploys:
node-stats-data:/app/data + NODE_STATS_ENV_FILE=/app/data/.env; - the installer stack is unchanged (its stack dir is durable).
Downloads
- NODE_STATS_ENV_FILE relocates the runtime .env for both reads