I've found it doesn't matter what HTTPD server you use.

You need to use separate installations for the Wordpress for each domain or sub domain. That way its able to be updated automatically by the users of the site... and make WordPress self updating.

Otherwise you'll step on everything "custom" and you'll be stuck updating from the repositories, while you'll be suck waiting for that when a zero day exploit comes along. Since its PHP and its an Application... its not very good combo.

Use a single HTTPD server (nginx or apache or whatever) with vhosts... and then separate installations of WordPress and then MySQL/Postgres.

Careful on the MySQL/Postgres stuff, since there have been specific exploit for PHP4+WP+certain versions of MySQL and PHP5+WP+certain versions of MySQL.

The "easy setups" are typically made for MySQL.

If he can get Postgres in the mix, it may or may not be available to him, since it requires some additional work.

replicating it where ever and setting up the vhost to recognize properly...

Its really a very cheap and easy setup.

Apache, if its only one instance, the "default" /var/www/html/ is all you need...

if you setup separate vhosts... minimal settings is really easy.

That way, people can update and maintain thier own install without any problems.


Doing it "apt-get" makes it tough to maintain without stomping on everything and resetting it up every time. Doing it with separate install its almost self maintaining.