On Mit, 26 Jan 2000, Emiliano wrote
> On Wed, 26 Jan 2000, David R Newman wrote:
>
> > 1. Put midgard-project.php3 somewhere other than /usr/lib/apache.
> > Ideally, scan /etc/httpd/httpd.conf for the line showing the top of the
> > Apache document tree, then put midgard-project.php3 in ../midgard
> > relative to that location.
>
> I don't reccomend the parent of the DocRoot. It's not guaranteed to
> be exclusive for apache. I reccommend the serverroot.
>
> In case of RPMs picking a location is going to be easy: the SuSE
> apache RPM is going to have things like the serverroot fixed anyway,
> so you can just put your stuff there without going through the
> httpd.conf.
Ok, since serverroot is "/usr/local/httpd" on SuSE 6.3, should I make the RPM
with midgard-project.php3 in this directory?
> > 2. Even better, write an install script for midgard-data, that copies the
> > sample images under that directory, writes to the end of httpd.conf the
> > lines needed for a simple, port based, Midgard set-up, and updates the
> > mysql and midgard databases according to these values. Ideally, get the
> > port numbers, IP addresses and machine names interactively from the user.
>
> Make conf for mod_midgard does part of that work for you. Install script
> is good idea, although interactivity is not really an option with RPMs,
> nor is passing options to the install process. Pretty stupid if you ask
> me but there ya go.
I thought that my RPMs modify httpd.conf in this way (simple sample setup) --
but it's not perfect since SuSE httpd.conf is full with strange <IfDef>
statements ;-)
But I don't think that RPM should make all the configuration, the user should
be able to customize the installation.
Malte
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
