Re: [RFD] gitweb configuration
- From
Junio C Hamano <junkio@cox.net>
- Date
- Jun 18, 2006, 08:38 UTC
- Message-ID
- <7v64iy505x.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <46a038f90606180042w7b4d11dbvbea28b750ddbc6e2@mail.gmail.com>
"Martin Langhoff" <martin.langhoff@gmail.com> writes:
Show 7 quoted lines
> 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).
I am not Pasky, but I think the intent of the patch is to run "git repo-config" with GIT_CONFIG pointing at /etc/gitweb.conf to obtain server-wide configuration (e.g. finding out where repositories are) and then when serving individual repository (i.e. after we set up GIT_DIR to point at it) run "git repo-config" without GIT_CONFIG to read per-repository configuration. That way we can reuse the configuration parser.