2078a0c828
This allows running gitweb as a separate user without needing to allow it read access to gitosis-admin.git. Running as separate user will still most likely require a ``chgrp www-data`` of the relevant repositories, but nothing not already decided public needs to be exposed. Existing gitweb users will need to adjust their gitweb.conf to point to the new location of the projects.list file. Removing the old projects.list from ~git/repositories/gitosis-admin.git/projects.list is safe once gitweb has switched to using the new location.
21 lines
839 B
Plaintext
21 lines
839 B
Plaintext
# Include the global configuration, if found.
|
|
do "/etc/gitweb.conf" if -e "/etc/gitweb.conf";
|
|
|
|
# Point to projects.list file generated by gitosis.
|
|
# Here gitosis manages the user "git", who has a
|
|
# home directory of /srv/example.com/git
|
|
$projects_list = "/srv/example.com/git/gitosis/projects.list";
|
|
|
|
# Where the actual repositories are located.
|
|
$projectroot = "/srv/example.com/git/repositories";
|
|
|
|
# By default, gitweb will happily let people browse any repository
|
|
# they guess the name of. This may or may not be what you wanted. I
|
|
# choose to allow gitweb to show only repositories that git-daemon
|
|
# is already sharing anonymously.
|
|
$export_ok = "git-daemon-export-ok";
|
|
|
|
# A list of base urls where all the repositories can be cloned from.
|
|
# Easier than having per-repository cloneurl files.
|
|
@git_base_url_list = ('git://example.com');
|