Date: Fri, 10 Mar 2000 00:35:13 -0500 (EST) From: "Matthew N. Dodd" <winter@jurai.net> To: "Scot W. Hetzel" <hetzels@westbend.net> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: FrontPage extensions on Apache Message-ID: <Pine.BSF.4.21.0003100026190.690-100000@sasami.jurai.net> In-Reply-To: <01a901bf8a50$87e7dec0$8dfee0d1@westbend.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 9 Mar 2000, Scot W. Hetzel wrote: > Now that I have the Apache13-FP port updated to the latest version and > building a package, I'll be working on the mod_frontpage port Sat/Sun. > Could yousend me your latest Apache ports so that I can be sure that > it operates properly with the mod_frontpage port. ftp://ftp.jurai.net/users/winter/ apache13.tgz mod_php4.tgz mod_ssl.tgz > Q. How are you handling the custom settings for each ports httpd.conf? Are > you putting them into <IfDefine port>...</IfDefine>? Actually installing ${PREFIX}/etc/apache/apache.conf.default-{php4,ssl,...} seemed like a better idea. > I have a patch for apachectl that allows you to define which ports modules > you want to use. > > i.e. apachectl start_FP_SSL_PHP3 > > apachectl will then start the server with "httpd -DFP -DSSL -DPHP3". Ah! Useful, though it may be nicer to suggest that the user simplify their life by setting up apache.conf correctly so that 'apachectl start' does what they want. This avoids the complication of having to accomidate all sorts of hacks to provide the ability for ports to register themselves with apachectl. > I was also thinking of fixing the apache Makefile so that it would use an > external Ports Config file: > > apache.ports: > frontpage FP > ssl SSL > php PHP3 > php4 PHP4 > jserv JSERV > > This way we wouldn't have to patch the main apache port's Makefile for each > new module port that gets submitted. You don't need to do anything with the apache port except install it to support additional modules built with APXS. > It would use this file to create the appropriate LoadModule/AddModule > <IfDefine port>..</IfDefine> entries in the httpd.conf-dist file. I don't think we need <IfDefine port> stuff at all. We install module specific apache.conf.default-foo and let the user tweak the stuff they want. I keep thinking that each module should come with a meta-file that presents all its configuration options in a format that a gui/web tool could parse and allow the user to configure stuff would be the way to go. > This file could also be used by the apache.sh script to determine which > modules exist on the system and to configure apache to use them. Ugh. Too much magic. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0003100026190.690-100000>