Hmm, there is no node-red in /usr/lib/node_modules
there is only one folder: npm
ok - lets go with sudo ln -s .npm-global/bin/node-red /usr/bin/node-red
PS - I have never seen this before... I have no idea how it got here...
That's what is worring me - again, when I try to install without using docker, there something messed up. Additionally, all retentive context data
All your flows should be safe in your .node-red directory, so don't touch that. (Or do but only to back it up).
Sorry about the last one - I just realized, I didn't backup settings.js so it defaults to not using the context storage in local file system. Plus all my authentication and SSL has gone in the bit, tuff, I was so focused on getting npm right I missed this. So far, it's back as the service. I noticed, one of the nodes stop working - node-red-contrib-modbus, I think i t has something to do with parallel tasking, but it's time to bed now (2am my time 
) Thanks for help @dceejay and @afelix
Just as aside - I had a problem with a Node-RED install on one of Pi - couldn't seem to sort it
So I used this
to create a separate running instance (changed port to 1881 in settings.js so it didn't conflict with original ) and got my flows working in it
I then eventually sorted the original one later on
2 Likes
