Keeping node.js servers up forever

I like how there's a command line interface plus an application interface, so I can tie forever process management into my web interface and backend control interface. Right now the processes are just sitting in a `while true` bash loop.

Re: Keeping node.js servers up forever

#5

Post by todd3834 » Thu, Dec 02, 2010, 8:11 AM UTC

I have been using supervisord to solve this problem. It doesn't care what language your app was written in and works very well.

Re: Keeping node.js servers up forever

#6

Post by dkasper » Thu, Dec 02, 2010, 8:15 AM UTC

Just deployed this now. Took all of roughly 10 seconds to setup and working beautifully. I've used supervisor in the past, and this was definitely easier.

Re: Keeping node.js servers up forever

#7

Post by indexzero » Thu, Dec 02, 2010, 8:26 AM UTC

substack wrote: post #4

I like how there's a command line interface plus an application interface, so I can tie forever process management into my web interface and backend control interface. Right now the processes are just sitting in a `while true` bash loop.

Thanks. If you dig in a little deeper you can see I use optimist for the CLI parsing :)

In the next version I'd like to expose a web service and also have hooks for doing things like sending emails when forever restarts a process.

Re: Keeping node.js servers up forever

#8

Post by gruseom » Thu, Dec 02, 2010, 8:27 AM UTC

By using the 'http' module we can run a stand-alone web server in node.js without the need for a separate server like Apache or nginx.

Last I checked Ryan was saying this was a very bad idea. Has that changed? It's certainly enticing.

Re: Keeping node.js servers up forever

#9

Post by indexzero » Thu, Dec 02, 2010, 8:38 AM UTC

gruseom wrote: post #8

By using the 'http' module we can run a stand-alone web server in node.js without the need for a separate server like Apache or nginx. Last I checked Ryan was saying this was a very bad idea. Has that changed? It's certainly enticing.

When did you last check with him? I've been running w/o a separate server (effectively) for ~3 months.

Re: Keeping node.js servers up forever

#10

Post by intranation » Thu, Dec 02, 2010, 8:39 AM UTC

This reminds me of the bad old days of Rails, when every man and his dog had some random hacky and myopic solution to keep Rails and Mongrel running. Just say no to Node/Rails/whatever specific-stuff, kids--use system level tools for running processes.

Edit: removed references to "proprietary", as indexzero is correct about meaning of that.