Installing builder 0.1.2 on Windows 7 pc - get the following.
Any thoughts? I'm on a University network so possibly a problem with it connecting to github? Is there a workaround?
Installing builder 0.1.2 on Windows 7 pc - get the following.
Any thoughts? I'm on a University network so possibly a problem with it connecting to github? Is there a workaround?
I believe this is your network proxy stopping you accessing the github site. If you switch to wifi you might be able to get around this?
Nope - no wifi adpter on the machine as suspected :(
npm version = 2.14.4
node version = 4.1.1
git version = 1.9.4.nsysgit.0
Sometimes there's a problem with the git:// protocol, and switching to using http(s):// will work.
Have a look at this StackOverflow question, which should help you to diagnose what's wrong.
Tom - amazing as ever.
So far so good but I get to the bit where it says :
You can see how this looks on file, by taking a peek at ~/.gitconfig
where you should now see that the following two lines have been added:
[url "https://"]
insteadOf = git://
but mine reports back with :
/m/.gitconfig: line 1: [user]: command not found
/m/.gitconfig: line 2: name: command not found
and it goes on down to 5 - /m/.gitconfig: line 5: insteadOf: command not found
I wonder if i'm looking in the wrong place for the config file?
You can see how this looks on file, by taking a peek at ~/.gitconfig
where you should now see that the following two lines have been added:
[url "https://"]
insteadOf = git://
AH might be something to do with git not in my PATH according to stack overflow. Will check...
We have the same problem, usually switching to wifi resolves it. If you don't have wifi could you tether your phone whilst you do the download?
We have a wifi connection available, but my machine has no wifi adapter, so it won't connect to a wifi network!
Hi Helen,
I'm not sure what the issue you're currently having is about, so I may be getting too far ahead here. But if the original problem was that the git protocol (ssh) really is blocked on your network, you may run into a similar problem later on with any node commands. If that happens, you can switch the http node registry like this:
npm config set registry http://registry.npmjs.org/
We had a similar issue on our our network, but configuring git and node to use http instead of ssh seemed to solve it. Sounds like there is something else in your git setup at the moment.
Well, between you all I think we cracked it to a point. I tethered my phone and used the registry.npmjs fix and it seems to have successfully completed the npm install.
EDIT! I just wasn't in the right folder and doing the right steps - it helps to ;)
Currently running npm install, then just node install and I should be up and running!!!!
Thanks so much guys just needed that nudge over the edge!
WOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
Helen