From owner-freebsd-isp  Mon Jan 24  8:48:15 2000
Delivered-To: freebsd-isp@freebsd.org
Received: from heaven.gigo.com (heaven.gigo.com [209.0.55.69])
	by hub.freebsd.org (Postfix) with ESMTP id 9B44915851
	for <freebsd-isp@FreeBSD.ORG>; Mon, 24 Jan 2000 08:48:11 -0800 (PST)
	(envelope-from jfesler@gigo.com)
Received: from heaven.gigo.com (heaven.gigo.com [209.0.55.69])
	by heaven.gigo.com (Postfix) with ESMTP
	id 283DB57F1; Mon, 24 Jan 2000 08:48:11 -0800 (PST)
Date: Mon, 24 Jan 2000 08:48:10 -0800 (PST)
From: <jfesler@gigo.com>
To: Stuart Henderson <sh@eclipse.net.uk>
Cc: freebsd-isp@FreeBSD.ORG
Subject: Re: Frontpage Extensions
In-Reply-To: <388C7DCB.E52002A@eclipse.net.uk>
Message-ID: <Pine.BSF.4.10.10001240845060.24978-100000@heaven.gigo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> So, run multiple apache binaries... your non-Frontpage customers
> would probably rather not to have anything involved with FP in the
> binary (or preferably server) that's serving their site anyway :-)

This I'll second.  If you want to even run it on the same server,
look at ProxyPass in apache - you can actually proxy entire virtual
sites to another server [which can be on a different port number].

I've done this trick more than once to avoid building the
UberApacheFromHell.  I keep my SSL seperate from my FP, since FP
always plays *so* nicely with other moduels  </sarcasm>, and it requires
fewer full builds and headaches whenever one module or the other needs
updating.






To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message