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.
> 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.
For post-install configuration you may want to take a peek at the
monster package spec which does another part of your proposal above.
> It took me quite some time to work out that I needed to turn
> CanonicalNames On,
Not necesary. AAMOF I have a number od setups where turning it off is
essential.
> then set up matching port numbers in three places in
> httpd.conf, and also in the midgard database.
Yes. The MP spec tries to be smart about this.
Note that if you have IPs to spare you don't need the extra Listen and
NameVirtualHost declarations.
emile
--
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]
