Forever’s documentation explains each briefly: –minUptime Minimum uptime (millis) for a script to not be considered “spinning” –spinSleepTime Time to wait (millis) between launches of a spinning script. A “spinning” application is one that keeps failing/crashing shortly after a restart. –minUptime sets the minimum amount of time that an application is expected to run. If … Read more
First of all you should skip the node thing in you command, it should not be there, you should not be able to execute that. forever automatically starts your script using nodejs. Instead you should do like this; sudo IS_PROD=1 forever app.js Probably you, instead of starting your server in foreground, will want to start … Read more
You should run something like this forever start -c nodemon app.coffee
add this styles animation-iteration-count: infinite;
If you want to pass node arguments from CLI then pm2 start myServer.js –node-args=”–production –port=1337″ . Edited you can add any arguments after — pm2 start app.js — –prod –second-arg –third-arg Sails docs for deploymemt.
EDIT: As of December 2018, this is no longer the correct way. See the other two answers. You need to symlink the nodejs executable to node sudo ln -s “$(which nodejs)” /usr/local/bin/node The reason for this is that when you do “apt-get install node”, it installs an unrelated package, so they had to choose a … Read more
Forever takes command line options for output: -l LOGFILE Logs the forever output to LOGFILE -o OUTFILE Logs stdout from child script to OUTFILE -e ERRFILE Logs stderr from child script to ERRFILE For example: forever start -o out.log -e err.log my-script.js See here for more info
I would suggest using crontab. It’s easy to use. How to To start editing run the following replacing the “testuser” with your desired runtime user for the node process. If you choose a different user other than yourself, you will have to run this with sudo. $ crontab -u testuser -e If you have never … Read more
First create your startup script @ /home/user/startup.sh, and make it executable chmod +x /home/user/startup.sh Then set a crontab for it: $ crontab -e @reboot /home/user/startup.sh Now your your startup.sh script will run at every start.