BetterCorp/BetterFrame
1
0
Fork 0
mirror of https://github.com/BetterCorp/BetterFrame.git synced 2026-05-26 19:06:34 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 10
BetterFrame/deploy/docker/Dockerfile.nodered

33 lines
1.3 KiB
Docker
Raw Normal View History

feat: bake BF Node-RED nodes into nodered Docker image - New deploy/docker/Dockerfile.nodered extends nodered/node-red, npm-installs the workspace nodered/ package into /usr/src/node-red/node_modules so bf-* nodes auto-load on boot. - docker-compose nodered service switched from public image to this build context. Rebuilding (--build) picks up node changes.
2026-05-12 23:57:26 +00:00
# BetterFrame Node-RED image with bundled BF nodes preinstalled.
#
# Extends official nodered/node-red, installs the workspace nodered/
fix: nodered settings.js nodesDir → /usr/src/betterframe-nodes Node-RED only scans userDir/node_modules by default. Setting nodesDir explicitly tells it to also scan our baked-in path, which survives the /data volume mount.
2026-05-13 00:00:40 +00:00
# package at /usr/src/betterframe-nodes. settings.js points nodesDir
# there so Node-RED scans it on boot. Survives /data volume mount.
feat: bake BF Node-RED nodes into nodered Docker image - New deploy/docker/Dockerfile.nodered extends nodered/node-red, npm-installs the workspace nodered/ package into /usr/src/node-red/node_modules so bf-* nodes auto-load on boot. - docker-compose nodered service switched from public image to this build context. Rebuilding (--build) picks up node changes.
2026-05-12 23:57:26 +00:00
FROM nodered/node-red:latest
USER root
fix: nodered settings.js nodesDir → /usr/src/betterframe-nodes Node-RED only scans userDir/node_modules by default. Setting nodesDir explicitly tells it to also scan our baked-in path, which survives the /data volume mount.
2026-05-13 00:00:40 +00:00
# Copy our nodes into a path outside /data (which is volume-mounted)
COPY nodered /usr/src/betterframe-nodes
feat: bake BF Node-RED nodes into nodered Docker image - New deploy/docker/Dockerfile.nodered extends nodered/node-red, npm-installs the workspace nodered/ package into /usr/src/node-red/node_modules so bf-* nodes auto-load on boot. - docker-compose nodered service switched from public image to this build context. Rebuilding (--build) picks up node changes.
2026-05-12 23:57:26 +00:00
fix(nodered): seed /data/settings.js via entrypoint wrapper The /data named volume hides anything Dockerfile COPYs into /data, so the previous CMD override pointing at /usr/src/bf-settings.js didn't help — Node-RED's launch script still looks for /data/settings.js by default, which doesn't exist after the volume overlays. Solution: entrypoint wrapper copies /usr/src/bf-settings.js to /data/settings.js on first boot when missing, then exec's npm start. Subsequent boots keep the user-edited version in the volume.
2026-05-19 01:57:42 +00:00
# Settings template + entrypoint that seeds /data/settings.js on first boot
# (the /data named volume hides anything we COPY directly there, so we have
# to plant the file after the volume mount comes up).
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 10:18:46 +00:00
COPY deploy/docker/nodered-settings.js /usr/src/bf-settings.js
fix(nodered): seed /data/settings.js via entrypoint wrapper The /data named volume hides anything Dockerfile COPYs into /data, so the previous CMD override pointing at /usr/src/bf-settings.js didn't help — Node-RED's launch script still looks for /data/settings.js by default, which doesn't exist after the volume overlays. Solution: entrypoint wrapper copies /usr/src/bf-settings.js to /data/settings.js on first boot when missing, then exec's npm start. Subsequent boots keep the user-edited version in the volume.
2026-05-19 01:57:42 +00:00
COPY deploy/docker/nodered-entrypoint.sh /usr/local/bin/bf-nodered-entrypoint
RUN chmod +x /usr/local/bin/bf-nodered-entrypoint
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 10:18:46 +00:00
fix: nodered settings.js nodesDir → /usr/src/betterframe-nodes Node-RED only scans userDir/node_modules by default. Setting nodesDir explicitly tells it to also scan our baked-in path, which survives the /data volume mount.
2026-05-13 00:00:40 +00:00
# Install deps for the nodes
RUN cd /usr/src/betterframe-nodes && \
npm install --omit=dev && \
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 10:18:46 +00:00
chown -R node-red:root /usr/src/betterframe-nodes /usr/src/bf-settings.js
feat: bake BF Node-RED nodes into nodered Docker image - New deploy/docker/Dockerfile.nodered extends nodered/node-red, npm-installs the workspace nodered/ package into /usr/src/node-red/node_modules so bf-* nodes auto-load on boot. - docker-compose nodered service switched from public image to this build context. Rebuilding (--build) picks up node changes.
2026-05-12 23:57:26 +00:00
fix(nodered): entrypoint runs as root to fix stale /data state, drops to node-red via su-exec Previous deploy left /data/settings.js as a DIRECTORY (Docker auto-mkdir from a failed bind mount earlier). cp from non-root user then failed 'Permission denied' writing inside it. Entrypoint now: - Detects + rm -rf the stale directory - Seeds /data/settings.js from /usr/src/bf-settings.js - Chowns /data to node-red - exec su-exec node-red:node-red to drop privileges before npm start
2026-05-19 02:00:58 +00:00
# Run entrypoint as root so it can fix stale /data state (e.g. /data/settings.js
# left as a directory by a previous broken bind mount). Entrypoint drops to
# node-red via su-exec before launching the actual server.
USER root
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 10:18:46 +00:00
fix(nodered): seed /data/settings.js via entrypoint wrapper The /data named volume hides anything Dockerfile COPYs into /data, so the previous CMD override pointing at /usr/src/bf-settings.js didn't help — Node-RED's launch script still looks for /data/settings.js by default, which doesn't exist after the volume overlays. Solution: entrypoint wrapper copies /usr/src/bf-settings.js to /data/settings.js on first boot when missing, then exec's npm start. Subsequent boots keep the user-edited version in the volume.
2026-05-19 01:57:42 +00:00
ENTRYPOINT ["/usr/local/bin/bf-nodered-entrypoint"]
CMD []
Reference in a new issue Copy permalink