okay found a small issue with starting node-red from rc.local it would cause an exception
Error: write EPIPE
but I notice that earlier if I ran it from rc.local it was like starting node-red under different user then starting it directly from root… so i guess a file it needs is locked under that condition…
so i wrote a small bash program that you load in cron it checks if node -red is running every couple minutes . if it running it does nothing if it not it starts node red
#!/bin/bash
if pgrep -x 'node-red' > /dev/null
then
echo "Node-Red is Running"
else
/usr/bin/node-red >> /root/iot.log & echo "Starting Node-Red"
fi
now everything runs much smoother - but I must say running under Openwrt LEDE is alot less resource hungry on my bananapi R1 under bananian OS with out desktop it was always around 20 -30 % CPU and 50% of the memory… now it runs at <4% cpu and 10% of memory and i am doing alot more in the background on openwrt then i was on bananian OS… but we will see how that changes once I fully enable snort.
oh if you wish to edit openwrt remote web port then you can set node-red to port 80
/etc/config/uhttpd
then
/etc/init.d/uhttpd restart
but most likely yo still have to reboot the device to allow for firewall setting to change before you can log in under different ports