git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Brian Mc Enery <moghroth@gmail.com>
To: git@vger.kernel.org
Subject: gitweb on MAC OSX 10.3 Panther
Date: Sat, 8 Sep 2007 15:05:44 +0100	[thread overview]
Message-ID: <9774728C-5E14-11DC-9B36-000A95EB57B4@gmail.com> (raw)

Hi there,

I have just completed the installation of gitweb (git version 1.5.3.1) 
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" \
         	all

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 \
		gitweb/gitweb.cgi

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

cp -fv  	./gitweb/gitweb.css \
         	./gitweb/git-{favicon,logo}.png \
         	/Library/WebServer/Documents/gitweb/res

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

Notes:

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 
/Library/WebServer/CGI-Executables/gitweb.


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 
username.

Relevant file permissions must of course be tweaked.

If all goes according to plan repositories are accessible from 
http://localhost/cgi-bin/gitweb/gitweb.cgi



Thank you,

Brían




Brían Mach Aon Innéirghthe
Corcaigh
Éire

                 reply	other threads:[~2007-09-08 14:12 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9774728C-5E14-11DC-9B36-000A95EB57B4@gmail.com \
    --to=moghroth@gmail.com \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).