> I'm still getting used to Apache, and security in that ;)
> (Sites are now happy to consider Apache as an alternative to IIS
> but it has been a hard slog)

Yeah, in my opinion that is the problem with Apache: it is hard to
install and configure just right. My aim for this package is to make
it easy to deploy intranet packages like PHProjekt into mid-market
accounts. If you want to host a major consumer e-commerce site, use
Apache. Horses for courses.

> > FB 1.5 client lib
> So you still need a Firebird installation?

Yes, if you want the FB server on that same machine. I figure there
are three cases:
- FB is already installed (FB user exploring PHP)
- FB not installed (PHP user exploring FB) & wants to use the
community FB installer
- FB not installed (PHP user exploring FB) & wants to use the
Fyracle installer
I chose not to force the PHP user into using Fyracle. Should I have?

> > Perhaps we should use PHP 5 instead of PHP 4/
> PHP4 is of little use with Firebird, only PHP5 has all of
> the 'nice' Firebird facilities surfaced in the module. I've been
> stung a couple of times with missing features when trying to
> maintain backwards compatibility.

I thought about that, but it was the feeling that many major PHP
packages were still dependend on PHP4. Has that changed in the last
months? Would you reckon that the PHP community has now by and large
moved across to PHP5 ?

> >>Will ibWebAdmin run on the package?
> > Yes, just unzip it into the C:\phpserver-0.8\web directory and
> > you are done.
> And try and set it up ;)
> It might be worth including THAT in the package - with a correctly
> configured 'configuration.inc.php' for the setup. It will give a
> good demonstration of what can be done with PHP!

Thought about that too, but the following held me back:
- what db-path should I config? Just to a demo db?
- how to find the path to isql & friends? I could make the installer
derive it from the global FIREBIRD env var on Windows, but how on
Linux?
Perhaps ibWebAdmin should have a config page so that the user can set
these paths without having to deep dive into configuration.inc.php

> ( I must get the demo site up to version 1.0, but it will be
> staying on Apache2 :) )

You mean that two shorts posts from a relative stranger was not
sufficient to make you throw out a trusted configuration in favour of
a development release? Man, you are conservative :^)