Git development
 help / color / mirror / Atom feed
From: nathan spindel <nathans@gmail.com>
To: Kevin Ballard <kevin@sb.org>
Cc: git@vger.kernel.org
Subject: Re: git-instaweb should 'just work' on Mac OS X
Date: Sat, 10 May 2008 16:19:29 -0700	[thread overview]
Message-ID: <F08C97B0-A7EE-4A32-9657-DCBDD291502A@gmail.com> (raw)
In-Reply-To: <D1BFDAC1-A959-44BD-A562-D787A68612B1@sb.org>

On May 10, 2008, at 3:49 PM, Kevin Ballard wrote:

> On May 10, 2008, at 2:27 PM, nathan spindel wrote:
>
>> 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?
>
> If I were to fix this, I'd suggest making apache2 work properly. I  
> patched the git-svn tests to do this a while back, so you could look  
> at what's I did there (3644da7214).

Thanks Kevin. Your patch is similar to how I imagined fixing apache2.

Would you suggest fixing the other non-starter issue (git-instaweb  
doesn't fallback to other daemons if the default doesn't exist)?  Or  
maybe changing the default to apache2 on Mac OS X installs (that seems  
like a poorer fix)?

-nathan

  reply	other threads:[~2008-05-10 23:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-10 19:27 git-instaweb should 'just work' on Mac OS X nathan spindel
2008-05-10 22:49 ` Kevin Ballard
2008-05-10 23:19   ` nathan spindel [this message]
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=F08C97B0-A7EE-4A32-9657-DCBDD291502A@gmail.com \
    --to=nathans@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kevin@sb.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