does not run on a Raspberry Pi Zero W after running installer script

[minizzZ]

Hello,

When I load your script onto a Raspberry Pi Zero W v1.1 or a Model B Revision 2.0 (512MB) I get this when starting up: "-bash: forever: command not found". Can these Raspberries not used for this script? It's updated and upgraded and on RASPBIAN STRETCH LITE | 2017-11-29.

[bmoren]

Did you run the installer script?

Did forever get installed? (you might want to switch this to pm2 or nodemon, I'll probubly do this when I update the script next) You can verify this by running forever --help. You should see the forever help menu.

Are you auto logging in using user Pi? (if you dont login using the pi user, the auto load will not work since NVM and Node will not be loaded since the paths are associated with that user. sudo raspi-config and change the boot options to command line (auto login as user pi)

[bmoren]

This is untested on a pi zero so ymmv. It should work fine as long as omxplayer works ok.

[CYOk]

I had the same issue. I had to buy Raspberry Pi 4B to get it to work...
When I ran the script to install on Pi Zero W, it printed a bunch of strangely long messages and the install process took more than half day. Then I ran the forever --help, I found out that it wasn't installed. Internet connection, power stability, and everything were normal. Tested on the different Zero Ws but no luck. But when I did the same process on RPi 4 it worked.
I am wondering why does it happen and if you could have a look into it.
I don't have a screenshot rn but I can post it if you are interested.

[bmoren]

you might try updating the installer version of NVM to the latest, modify this line:
wget https://raw.githubusercontent.com/creationix/nvm/v0.33.8/install.sh
with the correct latest one from here:
https://github.com/nvm-sh/nvm

It could be an incompatibility in the version of Nodejs that it's trying to install (32bit vs 64bit) since it's using an older installer. This is likely trying to install a version of nodejs from before the pi zero existed nvm @ 0.33.8 is from Dec 12 2017 so the architecture of the node install is likely wrong.

@CYOk can you confirm that node / npm were installed before attempting to run forever or install other things? did you have an error messages that you could post here?