-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation and linking with npm fails if folder is not owned by root on Linux #4
Comments
It may be a problerm of node-gyp. |
It's not a problem with node-gyp, in fact when I use --unsafe-perm this NPM works. |
Quite odd to close an issue without even trying to find the problem btw. |
FYI, I spoke with my colleague who figured out the --unsafe-perm workaround, and here is what he told me on IM:
|
Also:
|
Thanks for the information. |
ning-yu
pushed a commit
to volumio/Volumio2
that referenced
this issue
Feb 5, 2015
package.json - Add node-spotify - Add version and repo info NOTE: During node-spotify install, if build fails with error EACCES, you may need to run install with "sudo" or with flag "--unsafe-perm". See hideo55/node-murmurhash3#4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there
When I run the command
sudo npm link
your NPM is failing. However, when I run locally it works, but when I run on my Ubuntu server where there are non-standard permissions set on the application folder, the install fails. I have tried setting up the repository in the ubuntu home folder, and then runningsudo npm link
and it works fine, but when I put the repository in /var/[my app]/ and set permissions on those folders to allow a specific user and group, it no longer works.Do you have any idea what may be causing this?
Thanks for your help
Matt
Here is the output
The text was updated successfully, but these errors were encountered: