qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] https:// for GIT submodules / "smart" HTTP protocol on git.qemu.git
Date: Mon, 19 Mar 2018 15:10:28 -0400	[thread overview]
Message-ID: <20180319191028.GL12302@localhost.localdomain> (raw)
In-Reply-To: <20180319182816.GA18216@redhat.com>

On Mon, Mar 19, 2018 at 06:28:16PM +0000, Daniel P. Berrangé wrote:
> On Mon, Mar 19, 2018 at 04:49:39PM +0000, Daniel P. Berrangé wrote:
> > Most of QEMU regular developers are fortunate to have unfiltered internet
> > access which allows using the git:// protocol. People working in more
> > old fashioned / paranoid environments often find access to anything other
> > than http(s) blocked by firewalls. They'll get a bad experiance when trying
> > to build QEMU, when we try to initialize the git submodules and git://
> > protocol fails to connect.
> > 
> > We could improve life for people behind such nasty firewalls if we made our
> > GIT submodules use https:// URIs, instead of git:// URIs. There is one snag.
> > 
> > Historically git:// URIs were strongly preferred over http(s):// URIs for
> > reasons for performance. Modern GIT though, supports both the traditional
> > "dumb" HTTP protocol (which is horribly slow) and a modern "smart" HTTP
> > protocol whose performance matches that of git:/// URIs.
> > 
> > Unfortunately it seems that git.qemu.org is not configured to enable the
> > smart HTTP protocol.
> > 
> > So can we get a todo item for git.qemu.org get the web server setup to
> > enable the smart GIT protocol, so we can then enable use of http:// by
> > default for all the submodules to improve life for contributors.
> 
> FYI this doesn't seem to take much more than adding this to Apache
> config:
> 
>   SetEnv GIT_PROJECT_ROOT /path/to/git/projects/root
> 
>   <Directory /usr/libexec/git-core>
>    Require all granted
>   </Directory>
> 
>   ScriptAliasMatch "^/git/(.*\.git/(HEAD|info/refs))$" \
>     /usr/libexec/git-core/git-http-backend/$1
>   ScriptAliasMatch "^/git/(.*\.git/git-(upload|receive)-pack)$" \
>     /usr/libexec/git-core/git-http-backend/$1
> 
> 
> And then touching the file 'git-daemon-export-ok' in each git repo
> that is intended to be public.
> 
>   https://git.seveas.net/apache-gitweb-cgit-smart-http.html
> 

Daniel,

This is a good idea.  I'll look into implementing it (I'll wait until a time
of day that is relatively low-traffic).

-Jeff

      reply	other threads:[~2018-03-19 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 16:49 [Qemu-devel] https:// for GIT submodules / "smart" HTTP protocol on git.qemu.git Daniel P. Berrangé
2018-03-19 18:28 ` Daniel P. Berrangé
2018-03-19 19:10   ` Jeff Cody [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180319191028.GL12302@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).