On Wed, 11 Oct 2000, Greg Stein wrote:
> Not quite. It is also very easy to have a "little" directory under svn/
> which contains Apache. It can be preconfigured and set up specifically for
> SVN. As far as users are concerned, the fact that Apache is used could be
> completely invisible.
Yep, that would be totally kosher, though we'd need to be careful to
secure it down to turn off all unused functionality.
> > I'm realizing now that this situation could get annoying. For
> > example, I run FreeBSD. My FreeBSD distro has always automatically
> > loaded Apache on startup, but it always dies, because I've never yet
> > bothered to spend the time configuring my httpd.conf.
> Wow. On my Linux distro, it always works fine right out of the box. Somebody
> isn't paying attention in FreeBSD packaging land :-)
I've been installing apache from ports quite a bit, actually - they did a
reorg to split some modules out into their own ports instead of combo
ports. My only complaint is that it's not done in a menu-driven way to
select things like suexec and which modules to enable/disable, but that's
more apache's fault than freebsd. From a port, it's always been a simple
matter of make install then apachectl start for a basic setup.
> > The issue here for me is that a "repository" is (for now) a collection
> > of Berkeley DB files on disk. I shouldn't need Apache to use them.
> As long as our locking mechanism works between Apache access and local
> access, then this would be a Good Thing(tm) ... no question there.
Received on Sat Oct 21 14:36:10 2006