From: "Lars Hjemli" <hjemli@gmail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Johan Herland" <johan@herland.net>,
git@vger.kernel.org, "Jakub Narebski" <jnareb@gmail.com>,
"Kristian Høgsberg" <hoegsberg@gmail.com>
Subject: Re: CGit and repository list
Date: Sat, 13 Sep 2008 01:20:50 +0200 [thread overview]
Message-ID: <8c5c35580809121620x2de1828cq498b3709f7b0bd1b@mail.gmail.com> (raw)
In-Reply-To: <20080912224817.GF10360@machine.or.cz>
On Sat, Sep 13, 2008 at 12:48 AM, Petr Baudis <pasky@suse.cz> wrote:
> On Fri, Sep 12, 2008 at 06:12:40PM +0200, Johan Herland wrote:
>> On Friday 12 September 2008, Lars Hjemli wrote:
>> > On Fri, Sep 12, 2008 at 4:58 PM, Petr Baudis <pasky@suse.cz> wrote:
>> > > it seems that cgit
>> > > requires all the repositories explicitly listed in the config file.
>> > > Do you plan to remove this limitation in the future?
>> >
>> > Not really, I'd rather add another command (or a commandline option)
>> > to generate an include-file for cgitrc by scanning directory-trees
>> > for git repos. I've CC'd Kristian since I believe he's got such a
>> > script running for freedesktop.org; if so, maybe it could be
>> > included/used as basis for something similar in cgit?
>>
>> Here's a script I wrote for locating repos and generating repo
>> lists/configs for cgit, gitweb and hgwebdir (yes, this handles hg repos
>> as well). It works either as a CGI script (producing a list of detected
>> repos in HTML format), or from the command-line. It's only been tested
>> on an experimental DVCS server at $dayjob, so you might have to change
>> things to make it work in your scenario.
>>
>> If there is interest in this, I can create a public repo and we can keep
>> improving on it.
>
> Thanks. The script was a bit more scary than I thought, but in the end I
> managed to generate something. There are trailing dots in project names,
> but I'm not going to waste time on that anymore - this has long gone
> over the 20 minutes I originally alotted the project anyway; I hope cgit
> will gain a builtin capability for this in the future, since this is
> still quite a pain.
I guess I could add support for something like
scan-paths=/pub/git
in cgitrc (and optionally store the result of the scan as another
cgitrc-file in the cache directory). Would that improve things for
you?
> Unfortunately, the recommended RewriteRule is not working - it does not
> play well together with query parameters cgit is using, so e.g. browsing
> past commits does not work. What RewriteRule should I use instead?
On hjemli.net I used to specify "virtual-root=/git" in cgitrc combined
with this rule in /etc/apache/httpd.conf
RewriteRule ^/git/(.*)$ /cgit/cgit.cgi?url=$1 [L,QSA]
But currently I'm running the tip of the wip-branch (which has support
for PATH_INFO) on hjemli.net , so I've removed the "virtual-root" from
cgitrc and the rewriterule from httpd.conf and just use this instead:
ScriptAlias /git /var/www/htdocs/cgit/cgit.cgi
hth,
larsh
next prev parent reply other threads:[~2008-09-12 23:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 4:47 configuring git public repository sagi4
2008-09-12 12:33 ` Ciprian Dorin Craciun
2008-09-12 12:57 ` Jakub Narebski
2008-09-12 14:36 ` Lars Hjemli
2008-09-12 14:58 ` CGit and repository list Petr Baudis
2008-09-12 15:10 ` Lars Hjemli
[not found] ` <200809121812.40920.johan@herland.net>
2008-09-12 22:48 ` Petr Baudis
2008-09-12 23:20 ` Lars Hjemli [this message]
2008-09-13 19:49 ` Petr Baudis
2008-09-13 20:02 ` Lars Hjemli
2008-09-14 7:53 ` [CGIT PATCH] parsing.c: handle unexpected commit/tag content Lars Hjemli
2008-09-14 8:52 ` Lars Hjemli
2008-09-15 22:04 ` CGit and repository list Lars Hjemli
2008-09-14 17:14 ` Kristian Høgsberg
2008-09-14 17:22 ` Kristian Høgsberg
2008-09-14 18:01 ` Lars Hjemli
2008-09-12 15:54 ` Jakub Narebski
2008-09-12 16:00 ` Shawn O. Pearce
2008-09-12 16:12 ` Lars Hjemli
2008-09-12 16:05 ` Petr Baudis
2008-09-12 16:08 ` Shawn O. Pearce
2008-09-12 16:20 ` Petr Baudis
2008-09-12 16:22 ` Shawn O. Pearce
2008-09-12 17:40 ` Jakub Narebski
2008-09-12 17:45 ` Shawn O. Pearce
2008-09-12 19:13 ` Petr Baudis
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=8c5c35580809121620x2de1828cq498b3709f7b0bd1b@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
--cc=hoegsberg@gmail.com \
--cc=jnareb@gmail.com \
--cc=johan@herland.net \
--cc=pasky@suse.cz \
/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).