FredrikNoren / ungit

The easiest way to use git. On any platform. Anywhere.
MIT License
10.44k stars 637 forks source link

white blank page #182

Closed stolendog closed 10 years ago

stolendog commented 11 years ago

I run ungit. On console I get messages:

info: socket.io started info: Listening on port 8448 Browse to http://localhost:8448/#/repository?path=%2Froot%2Ftmp Took 766ms to start server.

Ungit started

but when I try to open on browser from my computer using url: http://192.168.2.3:8448/

I get white blank page, I can see html source on page using "view source" function of browser: <!DOCTYPE html>

ungit ....
FredrikNoren commented 11 years ago

Can you check the console output in the browser?

stolendog commented 11 years ago

I get:

NetworkError: 404 Not Found - http://192.168.2.3:8448/css/styles.css" styles.css "NetworkError: 404 Not Found - http://192.168.2.3:8448/js/ungit.js" ungit.js App version: undefined 192.168.2.3:8448 (line 496) "NetworkError: 404 Not Found - http://192.168.2.3:8448/js/ungit.js"

FredrikNoren commented 11 years ago

Sounds like your running it from the repository; have you followed the guide in the README.md? I.e. you need to run npm install, npm install -g grunt-cli and grunt

stolendog commented 11 years ago

I run grunt and get this:

Running "less:production" (less) task File public/css/styles.css created.

Running "browserify:dist" (browserify) task

Bundled public/js/ungit.js

Running "lineending:production" (lineending) task File "./bin/ungit" created. File "./bin/credentials-helper" created.

Running "imagemin:default" (imagemin) task Fatal error: ENOENT, no such file or directory 'public/images/branchIcon.png'

FredrikNoren commented 11 years ago

Sounds like something is funky with your clone; try just deleting your copy and re-checking out and follow the guide in the Readme (under Develop).

stolendog commented 11 years ago

I dont see public/images dir even on github repo (https://github.com/FredrikNoren/ungit/tree/master/public)

FredrikNoren commented 11 years ago

Nope its created as a part of the grunt build On 6 Sep 2013 13:18, "stolendog" notifications@github.com wrote:

I dont see public/images dir even on github repo ( https://github.com/FredrikNoren/ungit/tree/master/public)

— Reply to this email directly or view it on GitHubhttps://github.com/FredrikNoren/ungit/issues/182#issuecomment-23933358 .

slick666 commented 10 years ago

Having the exact same issue. From the console

Viewport argument key "" not recognized and ignored. localhost/:5 GET http://localhost:8448/css/styles.css 404 (Not Found) localhost/:6 Resource interpreted as Script but transferred with MIME type text/html: "http://localhost:8448/config.js". localhost:8448/:491 Resource interpreted as Script but transferred with MIME type text/html: "http://localhost:8448/version.js". localhost:8448/:491 App version: undefined localhost:8448/:496 GET http://localhost:8448/js/ungit.js 404 (Not Found) localhost:8448/:491

Running this on my laptop running Ubuntu. I installed npm from the repo and node from this link. https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager

I've duplicated this checking out 0.1.9, 0.2.0, and HEAD

FredrikNoren commented 10 years ago

@slick666 @stolendog are you guys intending to develop on ungit? Otherwise it's much easier to just npm install -g ungit than checking out the repository. If you are on the other hand planning on developing please see the instructions in the README (slick666 it looks like you haven't build ungit, see the docs)

slick666 commented 10 years ago

I think I was able to figure this out last night. I was interested in trying it because I thought it looked cool but having zero npm experience I didn't understand how I was making it harder for myself. @FredrikNoren perhaps we should put a short phrase or sentence at the top of the README summarizing your statement above to help point people in that direction.

Thanks for responding so quickly.

FredrikNoren commented 10 years ago

@stolendog let me know if using npm to install ungit doesn't solve the issues you were experiencing