No-, low- or all-code process automation.
https://www.youtube.com/watch?v=ksGeUD26Mw0&t=4s
Installation
Volumes
mkdir data
compose.yml
name: nodered
services:
node-red:
container_name: node
hostname: node
image: nodered/node-red:latest
user: "1000:1000"
restart: unless-stopped
environment:
- TZ=Europe/Berlin
networks:
- node-red-net
- caddy
volumes:
- ./data:/data
volumes:
node-red-data:
networks:
node-red-net:
caddy:
external: true
Reverse proxy
For Caddy:
node.handtrixxx.com {
reverse_proxy node:1880
}
Password
By default Node-RED runs unprotected, which of course does not work if we want to operate it in our private cloud. The password must be entered as a hash value into the settings.js file in the "data" volume.
We generate this from the host with the command:
docker exec -i node node-red admin hash-pw
We are then prompted to enter the password and receive the hash value for it.
Now we comment out the corresponding entry in settings.js and set it as follows:
adminAuth: {
type: "credentials",
users: [{
username: "WUNSCHNAME",
password: "HASHWERT",
permissions: "*"
}]
},
After saving, we restart the container once more so that these settings take effect.