| commit | f5988f9c2bfc5cb458a12a5a8aa04f4909f3fd54 | [log] [tgz] |
|---|---|---|
| author | Robert Kowalski <rok@kowalski.gd> | Fri Jul 31 21:39:09 2015 +0200 |
| committer | Robert Kowalski <rok@kowalski.gd> | Sat Aug 01 17:11:04 2015 +0200 |
| tree | 21fd3834cb82a7662e33b7d93ef3ff88b1915f59 | |
| parent | 35982a557a61ef04bb2ff66302dfe29be2e78fea [diff] |
explicitly look in home directory nvm installs node/npm and global modules into a subfolder in the users home. if you use the official nodejs installer it gets placed in /user/local - so the recursivve directory walker of config chain can't find it as it reaches / without passing the home dir fixes #1
nmo is a cli tool to manage CouchDB clusters and nodes.
npm install -g nmo
It is written in ES6 and is using promises and generators for control flow. We are aiming for 100% test coverage.
Production dependencies are checked in for multiple reasons:
bundledDependencies in the package.json file and npm just downloads one tarballnmo still works for new installs