nodester/nodester — pull request #319 by alejandromg (2012-02-28 04:58:36+00:00)
Title: [REV] Multiple node.js versions at nodester

### Multiple versions at nodester

Hi guys, I'm pushing some changes, to add ability to nodester for multiple versions of node. I was chatting with Chris and we decided to give to [`n`](http://github.com/visionmedia/n) a shot.

In short: `n` is a node version manager, based on bash. As we can see at the README, the use is pretty straightforward simple as this:

`n use app.js`

Also `n` is capable of working with npm as well:

`n npm moduleA moduleB and so on`

I've added also a easy script to install versions of node (I think a little bit unnecesary) but it can be very useful programatically.

The same as a new endpoint to check which versions are installed in nodester:

> curl -XGET http://api.nodester/env/version
{
"main":"0.4.11",
"available":["0.4.6","0.6.11","0.4.11",...]
}
> curl -XGET http://api.nodester/env/version/0.5.5
{
"main":"0.4.11",
"avaiable":["node-v0.5.5 it's not available, for the moment]
}

Also a `proxy_table` example, since it was missing, and fixed the install instructions (install.txt => install.md)

So, what I want is to you guys, with more experience at the nodester core, take a lot to what I did, and say in what maybe I'm doing it wrong or in which parts it should be a better approach.

EDIT: What I had problem is with the path of the `package.json` file, since sometimes it's chrooted, and other it doesn't, so it's kinda confussing, I hope it's ok.

**Cheers**
##### Alejandro Morales