HTTPS support? (need to use Github remotes)

[mhodgson]

Hey guys, nice work on Rugged, looks like it's coming along nicely. What is required to get a version of libgit2 with SSL working? Right now it's impossible to use github remotes since neither the https: or git: transports are supported. I'm happy to help if you can point me in the right direction.

Best,
Matt

[arthurschreiber]

Ah, I guess that comes from using the embedded libgit2, which in turn is compiled through Makefile.embed, which does not support ssh nor https.

What you could do:

Checkout libgit2 and build it through CMake with ssh and https support, and then install the rugged gem with the --with-git2-lib and --with-git2-include options.

[vmg]

Hm. I think it may be a good idea to allow extconf.rb to use CMakeLists.txt... This is a huge dependency (CMake) but there are already quite a few important features that simply don't get compiled in because we're using the embedded Makefile.

@mhodgson: the easiest way is to simply link with a hand-built version of libgit2 to ensure it has all the features you require (https, ssh, native crypto libs, whatever).

[mhodgson]

@vmg @arthurschreiber What is the current version of libgit2 that is compiled in the repo? If I try compiling head from libgit2 is that going to be a problem?

[vmg]

Rugged is always kept on sync with the head of the libgit2 development branch. We have a CI script that verifies the tests are clean and automatically bumps the version. We're brave like that.

[arthurschreiber]

You should build the same revision as the libgit2 submodule of your
rugged checkout. Or just use the code in the submodule. :)

[arthurschreiber]

Check out #261. It should build rugged/libgit2 with HTTPS and SSH support.

[johnbellone]

I am having troubles getting rugged to use libgit2 that I built from source with SSL support. Are there any instructions that are a little more detailed?

[arthurschreiber]

@johnbellone Can you try #261 and see if that works for you?

[johnbellone]

@arthurschreiber I am going to take a look tomorrow. I believe I finally got it built following the changes in #261.

[johnbellone]

I was able to successfully get it running it after a lot of attempts. I am not sure what the plan in the future is for the embedded version of libgit2 but it was a significant pain as I wasn't able to use bundle config and override like @arthurschreiber mentioned a few comments above.

But overall #261 definitely fixes the issue. It'd be nice to be able to specify the options in rake compile as I want to build the library with -DTHREADSAFE=ON as well.

[arthurschreiber]

@johnbellone I plan on wrapping up the work on #261 sometime this week, so this should not be an issue in the future.

Are you on rbx? If not, building libgit2 with -DTHREADSAFE=ON should not make any difference. Theoratically, I think we could always built a threadsafe libgit2, so there are no thread safety issues when using Rugged with Rubinius. But @vmg knows better than me whether that's right or not.

[ericfode]

+1 to #261 I am blocked on it also

[johnbellone]

@arthurschreiber Right now we are running on MRI 2.0.0 but we've been considering using Rubinius.

[arthurschreiber]

I'm closing this, as rugged nowadays supports anonymous https for clones, and with #292 it will also support authenticated https and ssh for cloning, as long as you build with CMake and have all dependencies installed.