OK - a few examples of use/misuse of the node-red command (or script) - /usr/bin/node-red:
Maybe some or all of these only happen on my Linux computer?
node-red admin rm
The script prints the Usage message
Usage:
node-red-admin <command> [args] [--help] [--userDir DIR] [--json]
Description:
Node-RED command-line client
Commands:
init - Interactively generate a Node-RED settings file
hash-pw - Creates a hash to use for Node-RED settings like "adminAuth"
target - Set or view the target URL and port like http://localhost:1880
login - Log user in to the target of the Node-RED admin API
remove - Remove the NPM module from Node-RED
etc
Excellent, I made a mistake and it told me about it.
-
node-red stop
ornode-red version
It happily assumes that I want to start Node-red using a flow file calledstop
orversion
. -
node-red --version
ornode-red -version
This seems to ignore the invalid parameter and starts Node-red using the defaultflows.json
-
node-red please start
Node-red starts up, expecting a flow file calledplease
. Anything else at the end of the command is silently discarded!
It seems to me that this part of the core does not adequately parse it's arguments and print appropriate feedback.
A glance at the other thread I linked to above shows that people are falling foul of this issue.