From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFD] gitweb configuration
Date: Sun, 18 Jun 2006 10:02:35 +0200 [thread overview]
Message-ID: <e731ai$su1$1@sea.gmane.org> (raw)
In-Reply-To: 46a038f90606180042w7b4d11dbvbea28b750ddbc6e2@mail.gmail.com
Martin Langhoff wrote:
> On 6/18/06, Jakub Narebski <jnareb@gmail.com> wrote:
>> So GIT_CONFIG would be ~/.gitconfig, and GIT_CONFIG_LOCAL would be
>> $GIT_DIR/config or what?
>
> I don't quite follow why gitweb needs a GIT_CONFIG_LOCAL defined.
> Given that it works in a CGI environment, it should read
> $GIT_DIR/config by default, and $GIT_CONFIG if set (from httpd.conf).
When talking about gitweb [installation] configuration, including where to
find GIT projects to display, one needs to remember that gitweb might (and
probably is) installed from binary package and not git.git, and
git/.git/config might not exist.
So we have the following options to separate gitweb-wide options:
- use ~/.gitconfig, /etc/gitconfig or some other global git configuration
file, reading values using '$gitexecdir/git-repo-config'.
Problem: bootstraping, namely value of $gitexecdir ($gitbin now)
needs to be set in gitweb.cgi, perhaps during the build process.
- use gitweb.conf for configuration, reading values via equivalent of
'GIT_CONFIG=gitweb.conf $gitexecdir/git-repo-config'.
Problem: bootstraping, namely value of $gitexecdir ($gitbin now)
needs to be set in gitweb.cgi, perhaps during the build process.
- use gitweb.conf for configuration, following the .git/config format,
writing parsing of ini file (reading only) in Perl from scratch
(or use one of many CPAN modules).
- use Perl for configuration file, a la Jon Loeliger <jdl@jdl.com> patch:
http://marc.theaimsgroup.com/?l=git&m=114308224922372&w=2
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-06-18 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 22:48 [RFD] gitweb configuration Jakub Narebski
2006-06-17 23:23 ` Petr Baudis
2006-06-18 4:00 ` Jakub Narebski
2006-06-18 7:42 ` Martin Langhoff
2006-06-18 8:02 ` Jakub Narebski [this message]
2006-06-18 8:30 ` Timo Hirvonen
2006-06-18 9:12 ` Jakub Narebski
2006-06-18 9:40 ` Junio C Hamano
2006-06-18 10:05 ` Jakub Narebski
2006-06-18 10:13 ` Martin Langhoff
2006-06-18 8:38 ` Junio C Hamano
2006-06-18 13:04 ` 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='e731ai$su1$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.