Git development
 help / color / mirror / Atom feed
From: nathan spindel <nathans@gmail.com>
To: git@vger.kernel.org
Subject: git-instaweb should 'just work' on Mac OS X
Date: Sat, 10 May 2008 12:27:38 -0700	[thread overview]
Message-ID: <B41867BF-1635-4611-9656-04F8C375BE61@gmail.com> (raw)

I've investigated what it would take for git-instaweb to 'just work' on
Mac OS X 10.5 when running the command with no arguments. This would be
of benefit to many Mac git users since they shouldn't be expected to
troubleshoot this problem. Here are the current issues at play:

  - lighttpd does not come with Mac OS X by default, so git-instaweb
    currently exits with "lighttpd not found...".

  - git-instaweb doesn't fallback to using other web servers on the  
system
    if the default command doesn't exist.

  - Mac OS X does come with webrick and 'git-instaweb -d webrick'  
_does_ just
    work. It's probably slower than Apache though (?).

  - Mac OS X also comes with mongrel, which is a great alternative, but
    git-instaweb doesn't support it.

  - Mac OS X's Apache installation is different than what git-instaweb
    expects in a couple areas:
    - the Apache binary is called 'httpd', not 'apache2', and git- 
instaweb
      only looks for the latter.
    - the modules on Mac OS X live in /usr/libexec/apache2 but by  
default
      git-instaweb looks for /usr/lib/apache2/modules.
    - Apache attempts to create its 'accept serialization lock file' at
      /private/var/run/ but that path is only writeable by root (a  
workaround
      is to add a LockFile directive to the conf file that places it
      in $fqgitdir/gitweb/tmp).

I'm interested in fixing this to make the experience smoother for Mac  
users.
What is the community's preferred avenue of fixing this?

-nathan

             reply	other threads:[~2008-05-10 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-10 19:27 nathan spindel [this message]
2008-05-10 22:49 ` git-instaweb should 'just work' on Mac OS X Kevin Ballard
2008-05-10 23:19   ` nathan spindel
2008-05-10 23:28     ` Kevin Ballard

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

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

  git send-email \
    --in-reply-to=B41867BF-1635-4611-9656-04F8C375BE61@gmail.com \
    --to=nathans@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox