Description
Two improvements:
- Add an option to start node-red in safe mode (a mode where the flow editor is available but it doesn't run any flows)
- Add an option to erase all thats on the data partition for signalk & node-red in order to be able to restart from scratch. DECIDED TO NOT DO THIS, WE ALREADY HAVE A RESET TO DEFAULTS FEATURE: THE FILE THAT CAN BE DOWNLODED ONTO A STICK OR SDCARD
@mansr to do all the work, except for the "Are you sure?" part, @jepefe has something for that in a draft somewhere from back in someday.
Safe mode:
If node-red becomes unavailable from the high load the web gui of node-red won't respond any longer.
Note that in that case disabling node-red from the console does not work (the process remains running):
# svstat node-red
node-red: up (pid 12571) 80 seconds, normally down, want down
Killing it from the commandline svc -k node-red does work.
To reproduce this (ie. a node-red being stuck), ask Dirk Jan.
When restarting node-red, there is a fair change that node-red becomes unresponsive again. In order to fix this, node-red ought to be started with the --safe option. The --safe option starts node-red with all of the flows disabled.
The idea is to add "safe mode" as a third option to the menu. So instead of just the on/off switch that we have now, have three options: Disabled, Enabled (normal), Enabled (safe-mode).
To use the safe mode, /usr/bin/node-red must be started with --safe as a flag.
Reset all Venus OS large feature to default.
Ie add a button, with Are you sure confirmation yes/no.
Once user says so, what must be done is:
- Down all venus os large services.
- `rm -rf /data/home/root/.node-red && rm -rf /data/conf/signalk``
- Bring the venus os large services back to the configured state.
reset feature to be added to bottom of menu here:
