From: "Alan Chandler" <alan@chandlerfamily.org.uk>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Alan Chandler <alan@chandlerfamily.org.uk>
Subject: [PATCH] Update the gitweb/README file to include setting the GITWEB_CONFIG environment
Date: Tue, 3 Oct 2006 22:48:46 +0100 [thread overview]
Message-ID: <11599121262709-git-send-email-alan@chandlerfamily.org.uk> (raw)
From: Alan Chandler <alan@chandlerfamily.org.uk>
Signed-off-by: Alan Chandler <alan@chandlerfamily.org.uk>
---
gitweb/README | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/gitweb/README b/gitweb/README
index 61c7ab5..099cfae 100644
--- a/gitweb/README
+++ b/gitweb/README
@@ -43,6 +43,7 @@ repositories, you can configure apache l
DocumentRoot /pub/git
RewriteEngine on
RewriteRule ^/(.*\.git/(?!/?(info|objects|refs)).*)?$ /cgi-bin/gitweb.cgi%{REQUEST_URI} [L,PT]
+ SetEnv GITWEB_CONFIG /etc/gitweb.conf
</VirtualHost>
The above configuration expects your public repositories to live under
@@ -51,6 +52,12 @@ both as cloneable GIT URL and as browsea
If you then start your git-daemon with --base-path=/pub/git --export-all
then you can even use the git:// URL with exactly the same path.
+Setting the environment variable GITWEB_CONFIG will tell gitweb to use
+the named file (ie in this example /etc/gitweb.conf) as a
+configuration for gitweb. Perl variables defined in here will
+override the defaults given at the head of the gitweb.perl (or
+gitweb.cgi). Look at the comments in that file for information on
+which variables and what they mean.
Originally written by:
--
1.4.2.1
reply other threads:[~2006-10-03 21:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=11599121262709-git-send-email-alan@chandlerfamily.org.uk \
--to=alan@chandlerfamily.org.uk \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).