forever

I am trying to set up forever-monitor. I added this to my app.js: var forever = require('forever-monitor'); var child = new(forever.Monitor)('app.js', { max: 3, silent: true, options: [] }); child.on('exit', function() { console.log('app.js has exited after 3 restarts'); }); child.start(); However when I start my application from the command line it logs 'app.js has exited after 3 starts' but it still runs. In which file should this code be placed? Am I missing something about the usage of forever-monitor? Here's how forever-monitor works app_fm.js var forever = require('forever-monitor'); var

I occasionally use forever.js for quick and dirty deploying of CLI type Node.js applications to production environments where I don't want a full on supervisord deployment. I was wondering if there was an equivalent for PHP? At the moment we have a queue processing system that get's messages from SQS and processes them synchronously into a database (it can't be done async as that causes all sorts of nasty row locking issues in this particular use case.) At the moment it runs ever minute using cron, but it often finishes early and I want it to start running again. I can't have more than one

CentOs 6.5 using root acount, I have a working Node.js Express app: root@vps [/home/test/node]# npm start app.js > test@0.0.1 start /home/test/node > node ./bin/www app.js The app can be seen working on the internet browser. I stop the app and try to run it with forever: root@vps [/home/test/node]# forever start app.js warn: --minUptime not set. Defaulting to: 1000ms warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms info: Forever processing file: app.js root@vps [/home/test/node]# Throws a couple of warnings that should not be a problem and looks

I use forever to launch my nodeJs server and I choose the log file : forever -l /home/api/log/api_output.log start server.js I use logrotate to move logfile every day (like advise here : NodeJS/Forever archive logs ), after one day my directory is like this : -rw-r--r-- 1 root root 0 avril 18 12:00 api_output.log -rw-r--r-- 1 root root 95492 avril 18 12:01 api_output.log-20140418 So, rotation is working, but the logs messages are now written in api_output.log-20140418, instead of api_output.log Maybe somebody can help me ? I forgot copytruncate option in my config file, now it's working : /etc