list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
* gitweb on MAC OSX 10.3 Panther
@ 2007-09-08 14:05 Brian Mc Enery
  0 siblings, 0 replies; only message in thread
From: Brian Mc Enery @ 2007-09-08 14:05 UTC (permalink / raw)
  To: git

Hi there,

I have just completed the installation of gitweb (git version 
on Mac OSX 10.3 Panther, and I thought that you may be interested in 
including  a note with your distribution, to enable an easier 
experience for others.

Essentially the commands I used were variations on the following.

****** Start installation of gitweb on Mac OSX ******

make    	prefix="/usr/local" \
         	PERL_PATH="/usr/local/ActivePerl-5.8/bin/perl" \

sudo      make prefix=/usr/local install

make   	PERL_PATH="/usr/local/ActivePerl-5.8/bin/perl" \
         	GITWEB_PROJECTROOT="/Library/WebServer/Documents/gitweb/rep" \
		GITWEB_CSS="/gitweb/res/gitweb.css" \
		GITWEB_LOGO="/gitweb/res/git-logo.png" \
		GITWEB_FAVICON="/gitweb/res/git-favicon.png" \
         	GITWEB_SITENAME="Local Git" \
		bindir=/usr/local/bin \

cp -fv  ./gitweb/gitweb.cgi /Library/WebServer/CGI-Executables/gitweb

cp -fv  	./gitweb/gitweb.css \
         	./gitweb/git-{favicon,logo}.png \

****** End installation of gitweb on Mac OSX ******


Perl_Path was necessary in order to change the shebang line in any perl 
or cgi scripts to use my non-standard
perl interpreter, i.e. different from usr/bin/perl.

The gitweb.cgi script and the configuration file gitweb_configure.perl 
must be placed in a directory under /Library/WebServer/CGI-Executables, 
as this is equivalent to localhost/cgi-bin. In this case I used 

The gitweb resources *must* be placed in a folder in 
/Library/WebServer/Documents, not in 
/Library/WebServer/CGI-Executables. In this case I placed the resources 
in  /Library/WebServer/Documents/gitweb/res, and used 
/Library/WebServer/Documents/gitweb/rep, as the project root. The 
absolute url for the project root must be specified.

In order to use symbolic links from a live project to the projectroot 
it was not necessary to make any changes to the Apache configuration 
file, however the files being linked to i.e. the project/.git files 
*must*(it took forever to work this out), be in a publicly accessible 
area, even if you are accessing using a browser under you own username. 
In my case I placed those projects in the Public folder, under my own 

Relevant file permissions must of course be tweaked.

If all goes according to plan repositories are accessible from 

Thank you,


Brían Mach Aon Innéirghthe

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2007-09-08 14:12 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-09-08 14:05 gitweb on MAC OSX 10.3 Panther Brian Mc Enery

Code repositories for project(s) associated with this inbox:

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 read-only IMAP folder(s) and NNTP newsgroup(s).