deploymeteor icon indicating copy to clipboard operation
deploymeteor copied to clipboard

/usr/bin/env: node: No such file or directory

Open ricksturgeon opened this issue 10 years ago • 3 comments

After running prepserver and during setup of application we see that /usr/bin/env: node: No such file or directory. When we look in env node is pointing to ~/.nvm/v0.10.26/bin/node which does not exist, nvm does not exist. We are running on an EC2 linix server.

Please give us an approach to resolve.

Rick

ricksturgeon avatar Jul 13 '14 13:07 ricksturgeon

You can try installing nvm on the server yourself and then rerun the app environment setup. Or you can use meteor-up to deploy instead. I think meteor-up is better than deploymeteor, so I don't put in much effort on this anymore, but I'll accept a PR if you figure out a solution.

aldeed avatar Jul 14 '14 14:07 aldeed

@ricksturgeon This is caused by nvm. I got rid of nvm altogether in the deploymeteor.sh and it worked like a charm. IMO, in production environment the node version management isn't really crucial. It makes more sense in the dev env.

jigyasam avatar Aug 31 '14 12:08 jigyasam

I think meteor-up is better than deploymeteor, so I don't put in much effort on this anymore, but I'll accept a PR if you figure out a solution.

It would be nice to make this clear somewhere in the readme perhaps, to help people like myself decide which to use.

kevb avatar Apr 29 '15 10:04 kevb