Dear list,
My gitweb has been running since long with a single project root, which
has been defined at the /etc/gitweb.conf through $projectroot variable.
I need one more project root for gitweb, hence I have added this apache config
( not a vhost, but just calling by alias)
````````````````````
SetEnv GIT_PROJECT_ROOT /home/newgit/
SetEnv GIT_HTTP_EXPORT_ALL
SetEnv GITWEB_CONFIG /home/newgit/gitweb.conf
#git is strict about the authenticated SSL certificate only
#disable the strict CA certificate check
SetEnv GIT_SSL_NO_VERIFY
AliasMatch ^/newgit/(.*/objects/[0-9a-f]{2}/[0-9a-f]{38})$ /home/newgit/$1
AliasMatch ^/newgit/(.*/objects/pack/pack-[0-9a-f]{40}.(pack|idx))$
/home/newgit/$1
ScriptAliasMatch \
"(?x)^/newgit/(.*/(HEAD | \
info/refs | \
objects/info/[^/]+ | \
git-(upload|receive)-pack))$" \
/usr/lib/git-core/git-http-backend/$1
#same location for gitweb
Alias /newgit /usr/share/gitweb
<Directory /usr/share/gitweb>
Options FollowSymLinks +ExecCGI
AddHandler cgi-script .cgi
</Directory>
#force https and authentication
<LocationMatch "/newgit">
# Require SSL connection for password protection.
SSLRequireSSL
AuthType Basic
# Message to give to the committer
AuthName "access requires a password"
# File listing users with write (commit) access
AuthUserFile /home/newgit/PASSWD
Require valid-user
</LocationMatch>
`````````````````````````````````````````SetEnv
But "SetEnv GITWEB_CONFIG" as well as other SetEnv ( like SetEnv
GIT_SSL_NO_VERIFY )
is not been taken and as an effect the gitweb processing the default
/etc/gitweb.conf and going to the
old projectroot.
What am I missing here ? any clue ?
Thanks
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120605112619.31d70...@shiva.selfip.org
