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

Docs - git:// blocked workaround #250

Closed
sindresorhus opened this Issue Feb 11, 2013 · 18 comments

Comments

Projects
None yet
@sindresorhus
Member

sindresorhus commented Feb 11, 2013

I think it could be useful for users if we documented how they can work around not being able to use the git protocol (company firewall, etc).

http://stackoverflow.com/a/10729634/64949

@geddski

This comment has been minimized.

Show comment
Hide comment
@geddski

geddski Feb 14, 2013

@sindresorhus this is a great workaround. Even better would be if Bower switched to using the https endpoint (at least for the public registry). Would there be any downsides to that?

geddski commented Feb 14, 2013

@sindresorhus this is a great workaround. Even better would be if Bower switched to using the https endpoint (at least for the public registry). Would there be any downsides to that?

@alvaromuir

This comment has been minimized.

Show comment
Hide comment
@alvaromuir

alvaromuir Feb 25, 2013

I agree. Unless I'm missing something (and I apologize if I am) maybe bower should default to https://github.com/xxx/xxx first?

I always have problems when at the office.

alvaromuir commented Feb 25, 2013

I agree. Unless I'm missing something (and I apologize if I am) maybe bower should default to https://github.com/xxx/xxx first?

I always have problems when at the office.

@alvaromuir

This comment has been minimized.

Show comment
Hide comment
@alvaromuir

alvaromuir Feb 25, 2013

Scratch last comment. I just read the workaround. That should be sufficient.

alvaromuir commented Feb 25, 2013

Scratch last comment. I just read the workaround. That should be sufficient.

@sindresorhus

This comment has been minimized.

Show comment
Hide comment
@sindresorhus

sindresorhus Feb 25, 2013

Member

@GEDDesign we can't do that, since we are git neutral and people submit in the format they want, and we can't assume an endpoint supports https.

Member

sindresorhus commented Feb 25, 2013

@GEDDesign we can't do that, since we are git neutral and people submit in the format they want, and we can't assume an endpoint supports https.

@geddski

This comment has been minimized.

Show comment
Hide comment
@geddski

geddski commented Feb 25, 2013

gotcha.

@engelke

This comment has been minimized.

Show comment
Hide comment
@engelke

engelke Feb 27, 2013

Just got bit by this. The problem is that I had no idea what was going wrong. Could bower at least try to fall back to https if git fails? That way, the user won't need to discover this workaround.

engelke commented Feb 27, 2013

Just got bit by this. The problem is that I had no idea what was going wrong. Could bower at least try to fall back to https if git fails? That way, the user won't need to discover this workaround.

@satazor

This comment has been minimized.

Show comment
Hide comment
@satazor

satazor Jul 18, 2013

Member

@engelke As @sindresorhus said, we can't assume the endpoint supports https.

Member

satazor commented Jul 18, 2013

@engelke As @sindresorhus said, we can't assume the endpoint supports https.

@sindresorhus

This comment has been minimized.

Show comment
Hide comment
@sindresorhus

sindresorhus Jul 18, 2013

Member

It's in the FAQ, but people apparently doesn't read it. We should put it in the readme since it's such a common problem.

Member

sindresorhus commented Jul 18, 2013

It's in the FAQ, but people apparently doesn't read it. We should put it in the readme since it's such a common problem.

@satazor

This comment has been minimized.

Show comment
Hide comment
@satazor

satazor Aug 4, 2013

Member

@sindresorhus or @necolas can one of you include it in the README so we can get this closed?

Member

satazor commented Aug 4, 2013

@sindresorhus or @necolas can one of you include it in the README so we can get this closed?

@satazor

This comment has been minimized.

Show comment
Hide comment
@satazor

satazor Aug 10, 2013

Member

We now translate git:// to https:// for GitHub endpoints when behind a proxy: #731
We can throw a more meaningful error message for other git endpoints.

Member

satazor commented Aug 10, 2013

We now translate git:// to https:// for GitHub endpoints when behind a proxy: #731
We can throw a more meaningful error message for other git endpoints.

@engelke

This comment has been minimized.

Show comment
Hide comment
@engelke

engelke Aug 11, 2013

Thank you. That seems like an excellent solution for people like me.

Charlie

On Sat, Aug 10, 2013 at 11:48 PM, André Cruz notifications@github.comwrote:

We now translate git:// to https:// for GitHub endpoints when behind a
proxy: #731 #731
We can throw a more meaningful error message for other git endpoints.


Reply to this email directly or view it on GitHubhttps://github.com//issues/250#issuecomment-22448089
.

engelke commented Aug 11, 2013

Thank you. That seems like an excellent solution for people like me.

Charlie

On Sat, Aug 10, 2013 at 11:48 PM, André Cruz notifications@github.comwrote:

We now translate git:// to https:// for GitHub endpoints when behind a
proxy: #731 #731
We can throw a more meaningful error message for other git endpoints.


Reply to this email directly or view it on GitHubhttps://github.com//issues/250#issuecomment-22448089
.

@satazor satazor closed this in 9141b30 Aug 16, 2013

satazor added a commit that referenced this issue Aug 16, 2013

Merge pull request #756 from bower/meaningful-proxy-error
Add additional message for proxy users about https//.insteadOf git://, fixes #250.
@luzfcb

This comment has been minimized.

Show comment
Hide comment
@luzfcb

luzfcb Oct 21, 2013

I needed to be able to use the bower on a network without proxy but with firewall that blocks a git port.

The solution I found was is:

http://stackoverflow.com/questions/15669091/bower-install-using-only-https

It would be nice to add a command line option to automatically make this change bower.

ps. Sorry for my english.

luzfcb commented Oct 21, 2013

I needed to be able to use the bower on a network without proxy but with firewall that blocks a git port.

The solution I found was is:

http://stackoverflow.com/questions/15669091/bower-install-using-only-https

It would be nice to add a command line option to automatically make this change bower.

ps. Sorry for my english.

@robdodson

This comment has been minimized.

Show comment
Hide comment
@robdodson

robdodson Mar 18, 2014

Asking people to modify their .gitconfig is not a good solution. Bower should either use https if the initial install was in https, ex: bower install https://path/to/thing, or it should attempt to fall back to https when git:// fails. It's very intimidating to people who are already not familiar with the command line to tell them to make some permanent change to a file they know little about (and will probably forget).

robdodson commented Mar 18, 2014

Asking people to modify their .gitconfig is not a good solution. Bower should either use https if the initial install was in https, ex: bower install https://path/to/thing, or it should attempt to fall back to https when git:// fails. It's very intimidating to people who are already not familiar with the command line to tell them to make some permanent change to a file they know little about (and will probably forget).

@nshew

This comment has been minimized.

Show comment
Hide comment
@nshew

nshew Jul 1, 2014

I'm going to second @robdodson's comment. This shouldn't require a change to another application (git) to work. It should be a self-contained option.

nshew commented Jul 1, 2014

I'm going to second @robdodson's comment. This shouldn't require a change to another application (git) to work. It should be a self-contained option.

@benschwarz

This comment has been minimized.

Show comment
Hide comment
@benschwarz

benschwarz Jul 2, 2014

Member

If a company firewall is blocking and git is blocked, bower should report the failure accordingly.

Changing the underlying configuration due to a firewall constraint should absolutely be undertaken by the user (and in many cases may have been already). Its an unrealistic expectation that bower should automagically deal with this issue.


As an asides, if bower was to favour https over git, or fallback to it, then we'd also have to not clone repos using shallow-clone, which means for slower initial clones, with more data transfer.


tldr, this is a tricky issue.

Member

benschwarz commented Jul 2, 2014

If a company firewall is blocking and git is blocked, bower should report the failure accordingly.

Changing the underlying configuration due to a firewall constraint should absolutely be undertaken by the user (and in many cases may have been already). Its an unrealistic expectation that bower should automagically deal with this issue.


As an asides, if bower was to favour https over git, or fallback to it, then we'd also have to not clone repos using shallow-clone, which means for slower initial clones, with more data transfer.


tldr, this is a tricky issue.

@jsdevel

This comment has been minimized.

Show comment
Hide comment
@jsdevel

jsdevel Jul 18, 2014

what about a setting in .bowerrc? git config ... is fine locally, but what if I have other package managers that depend on the default setting not being changed? Plus, I have to run this on Jenkins anytime I build which is a bit of a pain.

jsdevel commented Jul 18, 2014

what about a setting in .bowerrc? git config ... is fine locally, but what if I have other package managers that depend on the default setting not being changed? Plus, I have to run this on Jenkins anytime I build which is a bit of a pain.

@glenpike

This comment has been minimized.

Show comment
Hide comment
@glenpike

glenpike Sep 9, 2014

We have a problem where we are trying to use bower on an existing repository that uses git:// rather than https:// - if we change the .gitconfig, we get problems with our own git repo's. A setting in .bowerrc would be useful.

glenpike commented Sep 9, 2014

We have a problem where we are trying to use bower on an existing repository that uses git:// rather than https:// - if we change the .gitconfig, we get problems with our own git repo's. A setting in .bowerrc would be useful.

@sheerun

This comment has been minimized.

Show comment
Hide comment
@sheerun

sheerun Sep 9, 2014

Contributor

@glenpike I'm not sure if it works, but did you try changing .gitconfig in project's directory?

Contributor

sheerun commented Sep 9, 2014

@glenpike I'm not sure if it works, but did you try changing .gitconfig in project's directory?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment