gitweb: fallback to system-wide config file if default config does not exist
From a distribution point of view, configuration files for applications should reside in /etc/. On the other hand it's convenient for multiple instances of gitweb (e.g. virtual web servers on a single machine) to have a per-instance configuration file, just as gitweb currently supports through the file gitweb_config.perl next to the cgi. To support both at runtime, this commit introduces GITWEB_CONFIG_SYSTEM as a system-wide configuration file which will be used as a fallback if the config file sprecified throug GITWEB_CONFIG does not exist. See also http://bugs.debian.org/450592 Signed-off-by: Gerrit Pape <pape@smarden.org> Acked-by: Jakub Narebski <jnareb@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
committed by
Junio C Hamano
parent
1768905b51
commit
17a8b25005
@ -95,7 +95,11 @@ for gitweb (in gitweb/README).
|
||||
by default it is file named gitweb_config.perl in the same place as
|
||||
gitweb.cgi script. You can control default place for config file
|
||||
using GITWEB_CONFIG build configuration variable, and you can set it
|
||||
using GITWEB_CONFIG environmental variable.
|
||||
using GITWEB_CONFIG environmental variable. If this file does not
|
||||
exist, gitweb looks for a system-wide configuration file, normally
|
||||
/etc/gitweb.conf. You can change the default using the
|
||||
GITWEB_CONFIG_SYSTEM build configuration variable, and override it
|
||||
through GITWEB_CONFIG_SYSTEM environmental variable.
|
||||
|
||||
- Gitweb config file is [fragment] of perl code. You can set variables
|
||||
using "our $variable = value"; text from "#" character until the end
|
||||
|
||||
Reference in New Issue
Block a user