-
fix(raft): anchor the default data dir absolutely; image-based dokploy compose
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-11 23:05:29 +03:00 | 230 commits to main since this release'./data/raft' depends on the process working directory, which
orchestrator-managed deployments (dokploy & co.) don't guarantee —
'raft activate: create data dir: mkdir ./data/raft: no such file or
directory'. DefaultRaftDataDir() now resolves NODE_STATS_DATA_DIR/raft
when set, /app/data/raft inside a container (the compose-mounted data
volume), and keeps ./data/raft for native installs (systemd pins the
working directory). All five hardcoded default sites use it, and the
mkdir error now reports the cwd for diagnosability.Also adds docker-compose.linux-amd64.image.yml — the dokploy variant
running the prebuilt ghcr.io image instead of building from source, so
deploys don't hit Docker Hub's anonymous pull rate limit (429) on the
golang/node base images.Downloads