Node.js for Server Noobs

Main useful bits:

* cheap host, $10/month, root access so no configuration headaches. My search didn't turn up many of those, and the node hosting wiki page is non-obvious: http://github.com/ry/node/wiki/Hosting/_edit (and only just added webbynode to the list)

* how to set up that machine in particular

* points to other helpful resources once node is installed

./configure --with-abc --with-xyz --with-123=/in/some/place --without-something-else --disable-module --without-this-thing --and-everything-is-inconsistent

and then debugging paths, dependencies, realizing after 20 minutes of compilation that they're actually missing a module, editing php.ini and calling the president.

It's cool that articles like these actually highlight how easy deployment can be with Node. Thanks DTrejo!

I'd rather say: This is what people can work out without reading the doc. :-)

However, to be fair: The article links to various other articles which contain the "real" introduction, i.e. how to use node.js after it is installed.

If you want to do it all on one line, "apt-get update && apt-get upgrade" is the answer.

The && means "run the second command only if the first command completes without an error" .

My recommendation, as the developer of a SOAP client/server library; don't bother. Use Java or PHP, as those have the best SOAP libs out there, and figure out a way to pipe SOAP requests through your own java/php "proxy" app and let those libs take care of the cruft.

Using Node for SOAP is sacrilege. The two are diametrically opposed in their philosophies, and SOAP will easily negate any performance gains you might have made from using an event-drive server.