NodeJS in Production - Run at Startup and Restart if it Crashes

[Ken Snyder]

What is the best way(s) these days to run a NodeJS server in production; i.e. make sure that it runs at startup and restarts if it crashes.

Thanks,

Ken Snyder

[Ryan Florence]

s/if it crashes/when it crashes/

I use node-supervisor from izs (note: I have nothing very important running in node.)

Sent from my iPhone

--
Group meets on the 1st Thursday and 3rd Tuesday of each month. See http://utahjs.com/location/ for more info.
---
You received this message because you are subscribed to the Google Groups "Utah JavaScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email to utahjs+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/utahjs?hl=en-US.
 
 

[Sean Clark Hess]

Upstart on a Ubuntu box. It's really easy to use and I'm more comfortable using something non-node to keep node running. 

[Aaron S]

I use https://github.com/nodejitsu/forever

[Jamund Ferguson]

Yeah I also use forever.

I use https://github.com/nodejitsu/forever

--

[addisonj]

As Sean mentioned, upstart is quite amazing. As part time ops guy, I highly recommend it 

If you are deploying to ubuntu (or a debian with upstart), you can use https://github.com/idottv/gogogo for deploys. It will write out upstart files for you, has support for cron, deploying to multiple hosts, etc. 

If you have questions, feel free to email on list or directly.

On Saturday, May 18, 2013 8:04:43 PM UTC-6, Ken Snyder wrote:

[George Shank]

I use http://npm.im/forever as previously mentioned. It's incredibly easy to manage multiple daemon processes.

On Saturday, May 18, 2013 8:04:43 PM UTC-6, Ken Snyder wrote:

[Ken Snyder]

Thanks! It sounds like Upstart and Forever are the top picks.

--