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

Updated ReadMe Raspberry Pi Advanced (markdown)

Gareth and Naomi 2014-03-12 12:23:53 -07:00
parent 3dd409675d
commit e75ec5be7a
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ReadMe-Raspberry-Pi---Advanced.md

@ -80,6 +80,6 @@ I have tried to get forever working in a stable way on pi but have found it erra
If anyone has been successful please update this.
EDIT - We've been able to create an init script that uses forever to direct stdout and stderr to log files - 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 only switched to using forever approx. six weeks ago (24/7 usage in an embedded application).
EDIT - We've been able to create an init script that uses forever to direct stdout and stderr to log files - I've documented this here: http://l0l.org.uk/?p=179. I've also combined this with using monit to restart node-red automagically. So far we haven't seen any errors relating to the daemonising aspect, although we only switched to using forever approx. 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 just in case it helps update package dependencies. 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 I'm including it in case it does.