The core of our new project runs on Node.js. With Node you can write very fast JavaScript programs serverside. It's pretty easy to install Node, code your program, and run it. But how do you make it run nicely in the background like a true server?

Clever chaps will have noticed you can just use the '&' like so:

node ./yourprogram.js &

and send your program to the background. But:

• if Node ever prints something and your console is closed, the STDOUT no longer exists and yourprogram.js will die
• what if the process crashes, what if your server reboots?

Ok, so we needed something more robust. More like a real daemon, one that's recognized by the Operating System as such.

upstart

Our servers run Ubuntu's latest: Karmic Koala, which packs a pretty decent version of upstart. Upstart will eventually replace the well-known /etc/init.d scripts, and will bring some additional features to the table like: speed, health checking, simplicity, etc.

Writing an upstart script

Turns out, writing your own upstart scripts is way easier than building init.d files based on the /etc/skeleton file.

Ok so here's how it looks like; You should store the script in /etc/init/yourprogram.conf, create one for each Node program you write.

description "node.js server"
author      "kvz"
 
start on startup
stop on shutdown
 
script
    # We found $HOME is needed. Without it, we ran into problems
    export HOME="/root"
 
    exec /usr/local/bin/node /where/yourprogram.js 2>&1 >> /var/log/node.log
end script

Dont forget to chmod u+x your file so it will be executable.

Wow how easy was that? Told you, upstart scripts are childsplay. In fact they're so compact, you may find yourself changing almost every line cause they contain specifics to our environment.

non-root

Node can do a lot of stuff. Or break it if you're not careful. So you may want to run it as a user with limited privileges. We decided to go conventional and chose www-data.

We found the easiest way was to prepend the Node executable with a sudo like this:

exec sudo -u www-data /usr/local/bin/node

Don't forget to change your export HOME accordingly.

Restarting your Node.js daemon

This is so ridiculously easy.. 

start yourprogram
stop yourprogram

And yes, Node will already:

• automatically start at boottime
• log to /var/log/node.js

..that's been defined inside our upstart script.

initctl

But wait, start and stop are just shortcuts. Who's really behind the wheel here, is initctl. You can play around with the command to see what other possibilities there are:

initctl help
initctl status yourprogram
initctl reload yourprogram
initctl start yourprogram # yes, this is the same start

etc

More on Node.js

With Node you can write very fast JavaScript programs serverside. We've seen examples of chat, key-value store, and full blown http servers. Basically anything is possible as long as you know JavaScript and the concepts of parallel/evented processing. You don't? Well if you've ever used setTimeout(), you'll soon get the hang of it ; ) 

1. Node.js video presentation by creator Ryan Dahl
2. Node.js slides that accompany the presentation
3. About Node on the official website
4. Node.js is genuinely exciting by Simon Willison
5. node.js by Debuggable

Stay up to date

You can track my blog articles and comments. You may also find my bookmarks interesting. Or Follow me on Twitter