Closed owntheweb-archive closed 10 years ago
There is a fairly well known problem with OSX when installing packages globally. You may be able to get the packages installed globally (using sudo), but if any packages need to write to the filesystem (like monitor-dashboard), they won't have the authority (unless you sudo npm start monitor-dashboard).
Running everything under sudo isn't ideal, so my recommendation is to create a clean directory somewhere, cd to that directory, and install monitor and monitor-dashboard in that directory, using the same steps in the documentation, only omitting the '-g' flag to npm install.
In fact, I think I'll change the documentation to reflect that. There isn't any real reason to install globally other than a little convenience, and if everyone can't do it, it's not that convenient :)
How cool is that?! It works!!
Thanks for your lightning fast and detailed response. I was looking for a a great node.js example (and a server monitor for that matter).
I can't wait to dig and learn from your excellent work.
Hello, Pardon my node.js newbness in advance, but as I dive in, this project has me very excited (and puzzled at the moment). I'm running into errors when attempting to run monitor-dashboard. So far all is fine when running the monitor part.
Mac OSX 10.9
Quick guesses: [ ] Is my node.js too new? v0.10.22 [ ] Do I need to run at a higher admin level? "Please try running this command again as root/Administrator."
Warning when installing (Is my node.js too new?): sudo npm install -g monitor-dashboard
Errors after running npm start monitor-dashboard:
Log File:
I look forward to any feedback. Thanks for taking a look.