BetterFrame/deploy/docker
Mitchell R c8fa5d95a2
fix(deploy): bake configs into images — no host bind mounts
Coolify deployments don't always carry the full source tree on disk
at the bind-mount source path. Mounting a missing file lets Docker
auto-create a directory at the target, which then fails to mount over
the file the image expects.

Fix: bake config files into the images themselves:
- Dockerfile.server COPYs deploy/docker/sec-config.yaml → /app/server/.
  Env vars (BF_*) still override at runtime per env-overrides.ts.
- New Dockerfile.angie wraps nginx:alpine + baked betterframe.docker.conf.
- Dockerfile.nodered COPYs nodered-settings.js to /usr/src/bf-settings.js
  (outside the /data volume) and uses --settings to point at it.

Compose drops the three bind mounts; volumes are now strictly
runtime state (DB + secrets, Node-RED flows). Users who want a
different sec-config still get full control via env overrides or
Coolify's Storage UI.
2026-05-18 12:18:46 +02:00
..
Dockerfile.angie fix(deploy): bake configs into images — no host bind mounts 2026-05-18 12:18:46 +02:00
Dockerfile.nodered fix(deploy): bake configs into images — no host bind mounts 2026-05-18 12:18:46 +02:00
Dockerfile.server fix(deploy): bake configs into images — no host bind mounts 2026-05-18 12:18:46 +02:00
nodered-settings.js fix: nodered settings.js nodesDir → /usr/src/betterframe-nodes 2026-05-13 02:00:40 +02:00
sec-config.yaml feat(nodered): auto-provision bf-server-config on boot 2026-05-13 03:09:25 +02:00