revel/cmd

revel new is broken behind a corporate proxy

Closed this issue · 1 comments

Scenario:

$ echo $http_proxy $https_proxy
http://squid-proxy.mycompany.com:80 http://squid-proxy.mycompany.com:80
$ revel -v new -a github.com/myid/myrepo
INFO  08:50:37 command_config.go:140: Returned import path                     path=github.com/myid/myrepo buildpath=/home/myid/go 
Revel executing: create a skeleton Revel application
INFO  08:50:37 command_config.go:243: Source root                              path=/home/myid/go cwd=/home/myid/go/src/github.com/myid gopath=/home/myid/go 
INFO  08:50:37 command_config.go:257: Set application path                     path=/home/myid/go/src/github.com/myid/myrepo 
INFO  08:50:37 command_config.go:150: InitPackageResolver                      useVendor=false path=/home/myid/go/src/github.com/myid/myrepo 
INFO  08:50:37   file.go:313: error opening directory: open /home/myid/go/src/github.com/myid/myrepo: no such file or directory 
INFO  08:50:37    new.go:213: Detected skeleton path                   path=git://github.com/revel/skeletons:basic/bootstrap4 
INFO  08:50:37    new.go:245: Exec:                                    args="[git clone git://github.com/revel/skeletons /tmp/revel/skeleton]"

The process just hangs, going no-where.

SSH access (and therefore git clone git://) is also behind a socks proxy - the likely culprit here.

You might want to consider using git clone https:// which might work better in a http/https proxy environment.

In the next release the default method is git clone https:// ...