The documentation...

[gnimmelf]

Not really an issue, but more of a newbie request...

If you find time, I'd love to see a bit more verbose installation documentation; Examples, examples, examples =)

I'm green, no doubts, so I didn't even know if I was supposed to symlink to the url of nave.sh or not, since installing it didn't actually work out of the box (then I read the readme on my disk, and went "aaah!"). Once I figured out that "./nave.sh" worked, and symlinked to that, I am now stuck at "bin/nave use 0.3.4"; cause in the shell, typing "node" doesn't make anything happen:: "The program 'node' is currently not installed. You can install it by typing: sudo apt-get install node".

However, it seems s.th is happening in the shell when I try to run "node" from it's location: $> nave use 0.3.4 Already installed: 0.3.4 using 0.3.4 $> node $> exit exit failed somehow $>

-This "failed somehow" doesn't show up if I start and exit the shell w/o trying to run node...

Yup, a lot of whining about very basic stuff, but just wanna deploy my nodjs stuff easily, not learn unix (ok, I wanna learn unix, but not right now). Guessing perhaps there are a few unix-illiterate js-programmers heading over to nodejs these days, so, with npm and nave crystalising out of the modulejungle, it'd perhaps be an idea to be a little less brief in documenting the very basic stuff that actually gets nodejs servers into production the fastest...

Cheers for the excellent software and ideas.

[tutuca]

I'm not getting my mind around it either.

 $ nave use 0.3.6
    Already installed: 0.3.6
    using 0.3.6
 $ node -v
    v0.3.7-pre

I can exit without problems, so the subshell is activated.

[isaacs]

Perhaps you're setting your PATH explicitly in your .bashrc or .bash_profile, and thus overriding nave's setting? See the "Troubleshooting" section in the readme.