Strange symlink requirements for node/npm/parsoid install with non-root user

[jamesmontalvo3]

In VE.sh simply running npm install worked just fine under root. Under a non-root sudoer an "npm not found" error was given. To attempt to fix this, instead of using the symlink to npm at /usr/local/bin/npm the direct link to /usr/local/lib/node_modules/npm/bin/npm-cli.js was used. However, this resulted in a "node not found" error. To solve this a symlink was created to node (actual executable at /usr/local/bin/node) from /usr/bin/node. This allowed the process to function, though some of the tests failed everything was installed nominally.

What could cause this to happen?

A similar situation occurred first with Composer. The composer.phar file was moved to /usr/local/bin/composer per the documentation, such that it does not need to be envoked via php composer.phar <params> but instead just by composer <params>. This did not work, and instead during the initial install composer was always envoked by php ~/sources/composer.phar <params>.

Note that this only happens during the initial install, and that after the installer is done running composer, npm and node can be accessed without any issues.

[jamesmontalvo3]

Stack Overflow question posted: http://stackoverflow.com/questions/31332886/long-install-script-successful-as-root-npm-and-composer-not-found-as-non-root-s

[jamesmontalvo3]

Per response to SO question I tried running sudo env "PATH=$PATH" bash install.sh and it worked.

[jamesmontalvo3]

This should all be fixed by #79 and thus incorporated into v0.2

[jamesmontalvo3]

Closed with #79