-
Notifications
You must be signed in to change notification settings - Fork 5
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
JUTE start/stop issues with npm #5
Comments
Well the snipped you cut & pasted you did an 'npm config get jute:docRoot' instead of 'npm config set jute:docRoot' ?? |
I had set already. I just wanted to show the current docRoot value. |
ok cool - how about: % npm config set jute:docRoot .... -g ? |
I had to use sudo to set globally as followed. In any case, "npm restart jute -g" doesn't work for me. heightrush-lm:suite tester$ npm config set jute:docRoot /Users/tester/war/repos/quantum/sandbox/baechul/cocktails_taf/demo -g
heightrush-lm:suite tester$And "jute start", in case. heightrush-lm:suite tester$ jute start Looking for unit tests in: /var/www/test/ |
I noticed that if the docRoot doesn't exist then Mark, can JUTE throw or report errors in such cases, i.e., if its unable to start? |
JUTE start/stop instruction didn't work.
heightrush-lm:suite tester$ npm start jute -g
heightrush-lm:suite tester$ npm stop jute -g
heightrush-lm:suite tester$ npm restart jute -g
heightrush-lm:suite tester$ node --version
v0.4.11
heightrush-lm:suite tester$ npm --version
1.0.103
heightrush-lm:suite tester$
And not sure if the following ways are supported but at least it started the JUTE server.
heightrush-lm:suite tester$ npm config get jute:docRoot/Users/tester/war/repos/quantum/sandbox/baechul/cocktails_taf/demo
heightrush-lm:suite tester$ jute start
Looking for unit tests in: /var/www/test/
Ouptut going to: /var/www/output/
DMPING: {"port":8080,"docRoot":"/var/www","testDir":"/var/www/test/","outputDir":"/var/www/output/","java":"/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java","logFormat":"","testRegex":".html$","inject":1,"host":"","outputDirWeb":"output/","testDirWeb":"test/"}
Running as 501/20
Connect at http://heightrush-lm:8080/
I think obvious but 1 problem of this way is that it doesn't use configurations I set thru the npm. My docRoot was ignored and "/var/www" used instead.
The text was updated successfully, but these errors were encountered: