@flowfuse/nr-launcher v2.4.0
FlowFuse Launcher for Node-RED
This is the launcher FlowFuse uses to run instances of Node-RED. It dynamically generates the Node-RED settings based on the associated Project's settings.
The launcher starts its own HTTP service to allow the FlowForge platform to remotely control it.
Configure
--forgeURL
- URL for Forge platform--port
- port to listen on for management interface--team
- FlowForge team id UUID--project
- FlowForge project id UUID--token
- Bearer Token to access Forge platform--nodeRedPath
- path to dir with anode_modules
directory container a version of Node-RED--no-tcp-in
- inhibit TCP nodes from being servers--no-udp-in
- inhibit UDP nodes from being servers
The following Environment Variables can be used instead of the cmd line args...
FORGE_URL
, FORGE_TEAM_ID
, FORGE_PROJECT_ID
, FORGE_PROJECT_TOKEN
, FORGE_NR_PATH
, FORGE_NR_NO_TCP_IN
, FORGE_NR_NO_UDP_IN
NOTE: cmd line args take precedent if both are provided
By default, the launcher does not pass host environment variables through to the Node-RED process; only setting the built-in env vars and those configured in the instance settings.
However, if FORGE_EXPOSE_HOST_ENV
is set, the launcher will pass through all env vars - except that starting with FORGE_*
.
4 days ago
4 days ago
10 days ago
11 days ago
10 days ago
10 days ago
12 days ago
25 days ago
25 days ago
1 month ago
1 month ago
1 month ago
1 month ago
1 month ago
1 month ago
1 month ago
1 month ago
2 months ago
2 months ago
2 months ago
2 months ago
2 months ago
2 months ago
2 months ago
2 months ago
2 months ago
2 months ago
2 months ago
2 months ago
2 months ago
2 months ago
3 months ago
3 months ago
3 months ago
3 months ago
3 months ago
3 months ago
3 months ago
3 months ago
4 months ago
4 months ago
4 months ago
4 months ago
4 months ago
4 months ago
5 months ago
5 months ago
5 months ago
6 months ago
6 months ago
6 months ago
6 months ago
6 months ago
6 months ago
6 months ago
6 months ago
6 months ago
6 months ago
6 months ago