Foundation
-
FollowReplies
-
Problems using Foundation CLI
byBruno Monteiro Monday, November 25, 2013 at 10:15 AM EST
Hi,
After installing Foundation 5 I tried to use the new CLI to start a new project, but I did get the following errors:
foundation new styleguide_v3 --libsass
Creating ./styleguide_v3
create styleguide_v3
remote: Counting objects: 19, done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 19 (delta 3), reused 19 (delta 3)
Unpacking objects: 100% (19/19), done.
Installing dependencies with bower...
bower foundation#* ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/zurb/bower-foundation.git", exit code of #128
Additional error details:
fatal: unable to connect to github.com:
github.com[0: 192.30.252.128]: errno=Connection refused
/usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/foundation-1.0.2/lib/foundation/cli/generator.rb:68:in `read': No such file or directory - /Users/bruno/Sites/styleguide_v3/bower_components/foundation/scss/foundation/_settings.scss (Errno::ENOENT)
from /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/foundation-1.0.2/lib/foundation/cli/generator.rb:68:in `block in new'
from /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/thor-0.18.1/lib/thor/actions.rb:182:in `block in inside'
from /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/2.0.0/fileutils.rb:125:in `chdir'
from /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/2.0.0/fileutils.rb:125:in `cd'
from /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/thor-0.18.1/lib/thor/actions.rb:182:in `inside'
from /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/foundation-1.0.2/lib/foundation/cli/generator.rb:65:in `new'
from /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/thor-0.18.1/lib/thor/command.rb:27:in `run'
from /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/thor-0.18.1/lib/thor/invocation.rb:120:in `invoke_command'
from /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/thor-0.18.1/lib/thor.rb:363:in `dispatch'
from /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/thor-0.18.1/lib/thor/base.rb:439:in `start'
from /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/foundation-1.0.2/bin/foundation:4:in `<top (required)>'
from /usr/local/opt/ruby/bin/foundation:23:in `load'
from /usr/local/opt/ruby/bin/foundation:23:in `<main>'
Does anyone have an idea of what's going on? This happens using --libsass option AND without that option.
Thanks.
Mihai Stroe
about 6 years ago
It seems that you cannot connect to github.com, do you also have git installed on your system? If so perhaps try updating your Foundation CLI (current version is 1.0.4).
Brad Bodine
about 6 years ago
from the command line do a GIT VERSION . If git is installed and working it should list it. That will at least verify that git is installed on your machine and in the path.
Victor Toh
about 6 years ago
Hi I also have exactly the same issue, but I've got the foundation (bower?) CLI v1.0.4 and Git 1.8.3.4 (Apple Git-47).
If I try to use the command 'foundation new MY_PROJECT' or 'foundation update' it would eventually result in:
bower ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/zurb/bower-foundation.git", exit code of #128
Additional error details:
fatal: unable to connect to github.com:
github.com[0: 192.30.252.129]: errno=Operation timed out
In my searching for a solution a few weeks ago, I thought I read somewhere that it might be something to do with conflicting versions of ruby I've got installed...
The problem is, I lost the page and can't seem to find it again. I'm not familiar at all with ruby or bower.
Any help would be appreciated.
Aldren Espejo
about 6 years ago
Hi
I think I encountered the same error last week when I'm creating a new project using foundation 5. What I did was to use the latest Ruby version. Current system requirements for F5 are Git, Ruby 1.9+ and NodeJs.
Before I was using 1.8 and I updated it to 1.9 and everything works perfectly. You can check your ruby version using ruby -v command.
Bruno Monteiro
about 6 years ago
Actually, the problem was related with bower which is using port 9418 for the git protocol.
My company sysadmin had that port closed.
Thomas Hoadley
almost 6 years ago
I had this problem aswell. Try uninstalling git and then reinstalling the latest version (http://git-scm.com/) and then during installing tick 'Run Git from the Windows Command Promt' instead of 'Use Git Bash only'. As long as you have the correct node.js and bower installed you should now be able to use 'foundation new PROJECTNAME' to start your project!
Sherwin Techico
almost 6 years ago
This is a tweak of the previous comment via https://coderwall.com/p/sitezg
"You can also limit this URL rewriting to an explicit list of Git repos that are outside your firewall. This way you can still use the git:// scheme inside your LAN with your internal repos."
git config --global url."https://github.com".insteadOf git://github.com
+1