From: Jon Loeliger Date: Sun, 04 Jun 2006 00:13:45 GMT Subject: git daemon directory munging? Message-ID: Scrapped right off the #git IRC channel... I stumbled across some git-daemon quirk for which I'd like opinions on possible solutions. [18:56] I run a server that houses multiple virtual hosts on one physical machine. It has multiple Apache based websites on it, and I want to front multiple git repositories with gitweb. That all works fine. [18:57] But when I set up my repository stores, ie the /pub/scm/repo.git places, it falls apart. I want to maintain separate sets of git repos for each virtual site. [18:58] That is, www.foo.com can't see the repos of www.bar.com and vice versa. So I have an Apache directory set up that maps www.foo.com/pub/scm to some place like /pub/foo/scm using an alias for /pub/scm. [18:59] Similarly, for www.bar.com I map /pub/scm to /pub/bar/scm Now, when I clone using http: all is well as it correctly maps the URL using the Apache Alias entry. [19:00] However, when cloning via git: it doesn't do the Alias mapping based on the given website prefix part of the URL. I would have to clone using git://www.foo.com/pub/foo/scm even though I would clone using http://www.foo.com/pub/scm/ [19:01] So my proposed solution is to setup a genarlization of the git-daemon -baser-path=path argument. Instead of a single --base-path, there are potentially multiple --base-path entries that match multiple a URL prefixes. [19:02] Thus, I'd use something like: --map-base=www.foo.com/pub/scm:/pub/foo/scm --map-base=www.bar.com/pub/scm=/pub/bar/scm [19:04] mod_rewrite for git :| Quick prefix hack, yeah. [19:05] Um, stop me before I hack....? :-) [19:06] you're going to end up needing something that supports basic regexes before long I can't think of many cases where you'd want to directly map like that, and especially in that specific manner. [19:07] I can't hear you. sorry. * dormando was going to have similar problems for his hosting service