rugged
rugged copied to clipboard
libgit2
Proxy support for HTTP transport for `.clone_at` in rugged?
Is there any chance to support HTTP-transport via proxy in rugged for Rugged::Repository.clone_at('http://example.org/repo.git')? There's an issue open at libgit2/libgit2#2555, but maybe that would be something which can / needs to be "fixed" in rugged itself.
Cheers, dg
Hey @dg-ratiodata,
Support in Rugged will only be possible after the support for http proxies was implement in libgit2.
Ok. Thanks for the reply. :-)
Do you know if https://libgit2.github.com/libgit2/#HEAD/group/transport would be the correct place where one needs to implement a suitable transport mechanism? Sorry for asking that, but I'm not familiar with libgit2 and C either.
From what I understand, http(s) connections that make use of libcurl will honor the http_proxy and https_proxy environment variable correctly. Unfortunately, there's no runtime support for setting this configuration yet - https://github.com/libgit2/libgit2/pull/3110 is supposed to resolve that, but it's still pretty much a work-in-progress.
To summarize: If you run on linux, use rugged 0.23 or later, and have the libgit2 bits compiled to use libcurl, proxies for http and https should work based on what is defined in the http_proxy or https_proxy environment variables.
