Skip to content
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

quarks (new) - suggestion - directory.txt use https instead of git protocol. #1397

Closed
miguel-negrao opened this issue Apr 1, 2015 · 4 comments
Assignees
Labels
comp: help schelp documentation enhancement good first issue indicates issue tickets that are suitable for a new contributor quarks
Milestone

Comments

@miguel-negrao
Copy link
Member

Using the git protocol (git://) will try to open port 9418.

tcp        0      1 143.117.230.148:52195   192.30.252.130:9418     SYN_ENVI    1000       44131       12311/git 

On many netwoks, specially university networks in the uk, that port is blocked. I for instance cannot use the quarks from the university wireless. That causes the git process to just hang. Wouldn't it be better to use https instead ? Htttps is almost never blocked (thank god for online banking !).

@crucialfelix
Copy link
Member

I was wondering about that too.

If we change it we will probably break a few installs, but its best to
change it now.

On Wed, Apr 1, 2015 at 11:40 AM Miguel Negrão notifications@github.com
wrote:

Using the git protocol
http://git-scm.com/book/es/v2/Git-on-the-Server-The-Protocols (git://)
will try to open port 9418.

tcp 0 1 143.117.230.148:52195 192.30.252.130:9418 SYN_ENVI 1000 44131 12311/git

On many netwoks, specially university networks in the uk, that port is
blocked. I for instance cannot use the quarks from the university wireless.
That causes the git process to just hang. Wouldn't it be better to use
https instead ? Htttps is almost never blocked (thank god for online
banking !).


Reply to this email directly or view it on GitHub
#1397.

@scztt
Copy link
Contributor

scztt commented Apr 18, 2015

I just learned that the workaround for this is to run:
git config --global url."https://".insteadOf git://
...which redirects all git:// urls to https:// urls.
For 3.7, we should add this to the documentation and possibly to an error message if it appears our git connection is failing.

@scztt scztt added this to the 3.7 milestone Apr 18, 2015
@scztt scztt added good first issue indicates issue tickets that are suitable for a new contributor comp: help schelp documentation labels Apr 18, 2015
@gusano
Copy link
Member

gusano commented Apr 18, 2015

@crucialfelix why would using https:// instead of git:// break a few installs?

@crucialfelix crucialfelix self-assigned this Jun 16, 2015
@crucialfelix
Copy link
Member

I don't think we break any installs at all if we just change it. but it might reinstall them because the url doesn't match. it would put them in the same location.

I'll just find and replace them all and change quarks docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp: help schelp documentation enhancement good first issue indicates issue tickets that are suitable for a new contributor quarks
Projects
None yet
Development

No branches or pull requests

4 participants