frodovdr/node-red
1
0
Fork 0
mirror of https://github.com/node-red/node-red.git synced 2023-10-10 13:36:53 +02:00
Code Issues Releases Wiki Activity

Added reference to init script for daemonising node-red with forever

Gareth and Naomi 2014-03-12 10:49:35 -07:00
parent 8dd406f435
commit e413782038
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ReadMe-Raspberry-Pi---Advanced.md

@ -78,4 +78,8 @@ Forever's ability to restart automatically would be useful, especially during de
I have tried to get forever working in a stable way on pi but have found it erratic. It did not always daemonise and started throwing stdout onto the console despite the -o or -a switch. I suspect version incompatibilities although npm does not complain.
If anyone has been successful please update this.
If anyone has been successful please update this.
I've been able to create an init script that uses forever to direct stdout and sterr to log files so that I can review them - I've documented this here: http://l0l.org.uk/?p=179. So far we haven't seen any errors relating to the daemonising aspect, although we've only switched to using forever six weeks ago (24/7 usage in an embedded application).
Due to my limited understanding of npm I have been in the habit of running sudo npm update after finishing package installations. I'm not sure if that has actually updated anything or not tbh, nor if this sheds any light on the experiences of others, but including it in case it does.