Skip to content
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.

I am missing a link to /usr/local/bin/node #37

Closed
arabus4chip opened this issue Jan 31, 2014 · 8 comments
Closed

I am missing a link to /usr/local/bin/node #37

arabus4chip opened this issue Jan 31, 2014 · 8 comments
Labels

Comments

@arabus4chip
Copy link

i have a link to /usr/local/bin/node-v0.10.25 from /usr/local/node/node-v0.10.25/bin/node
But now i cant just use "node" in further recipes and don't know how to create that as i need the version number that is only available in the module...

Did i miss something?

@grafjo
Copy link
Contributor

grafjo commented Jan 31, 2014

hey!

do you need multiple installed versions of node? If not use the class instead of the define!
The class is managing /usr/local/bin/node and /usr/local/bin/npm
e.g.

class { 'nodejs':
  version => 'stable',
}

@willdurand
Copy link
Owner

@grafjo We probably need to make things clear in the README. WDYT?

@grafjo grafjo mentioned this issue Feb 1, 2014
@grafjo
Copy link
Contributor

grafjo commented Feb 1, 2014

@willdurand hope this will solve this issue?

@arabus4chip
Copy link
Author

First: Thanks for the quick answer,
but...

i used a class already:

 class { 'nodejs':
      version => 'stable',
      make_install => false,
      target_dir => "/usr/local/bin",
   }

the target_dir was an attempt to get it installing the node bin.
Perhaps the make_install dies sth differently?

Thanks....

@arabus4chip
Copy link
Author

Oh, no i need only one version of node but i wanted the latest stable, so version = stable was in there form the beginning.

@willdurand willdurand reopened this Feb 3, 2014
@grafjo
Copy link
Contributor

grafjo commented Feb 3, 2014

@willdurand I removed /usr/local/bin/node, it's now /usr/local/node/node-default/bin/node and published via $PATH. Just node-$version is linked to target_dir

@arabus4chip
Copy link
Author

Got it.
That's a tiny bit hard to find, but makes sense...

i think my tests with "vagrant provision" failed because the PATH was not updated in the ssh shell session.
"vagrant destroay && vagrant up" worked like intended.

Thanks for the clarification.

@grafjo
Copy link
Contributor

grafjo commented Feb 3, 2014

Just updated the README to be more clear on this point

@grafjo grafjo mentioned this issue Feb 3, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants