git-commit-vandalism

History

Jeff King c8d138a8c0 gitweb: optionally read config from GITWEB_CONFIG Configuration will first be taken from variables inside the gitweb.cgi script, which in turn come from the Makefile. Afterwards, the contents of GITWEB_CONFIG are read, overriding the builtin defaults. This should eliminate the need for editing the gitweb script at all. Users should edit the Makefile and/or add a config file. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <junkio@cox.net>		2006-08-02 13:56:34 -07:00
..
test	Merge git://git.kernel.org/pub/scm/git/gitweb	2006-06-10 11:20:59 -07:00
git-logo.png	gitweb: use out-of-line GIT logo.	2006-08-01 15:55:19 -07:00
gitweb.css	gitweb: Refactor generation of shortlog, tags and heads body	2006-07-31 03:09:28 -07:00
gitweb.perl	gitweb: optionally read config from GITWEB_CONFIG	2006-08-02 13:56:34 -07:00
README	gitweb/README: do not bug Kay with gitweb questions anymore	2006-08-01 15:56:28 -07:00

README

GIT web Interface

The one working on:
  http://www.kernel.org/git/

From the git version 1.4.0 gitweb is bundled with git.


How to configure gitweb for your local system:

You can specify the following configuration variables when building GIT:
 * GITWEB_SITENAME
   Shown in the title of all generated pages, defaults to the servers name.
 * GITWEB_PROJECTROOT
   The root directory for all projects shown by gitweb.
 * GITWEB_LIST
   points to a directory to scan for projects (defaults to project root)
   or to a file for explicit listing of projects.
 * GITWEB_HOMETEXT
   points to an .html file which is included on the gitweb project
   overview page.
 * GITWEB_CSS
   Points to the location where you put gitweb.css on your web server.
 * GITWEB_LOGO
   Points to the location where you put git-logo.png on your web server.

Originally written by:
  Kay Sievers <kay.sievers@vrfy.org>

Any comment/question/concern to:
  Git mailing list <git@vger.kernel.org>