General ideas from a Web Applications Debian Policy

-- Database

Posible Solution I: mysql-server (>= 4.0.20-8) now features a debian-sys-maint super user which can setup mysql users and databases.

Posible Solution II: Some sort of ODBC-alike registry of available database engines (which is why it's not ODBC) where we have the configuration for each DB server available to the machine, and when a package is installed, a list of the available database servers comes up and asks "where do you want this?". If there's only one (as there would be by default if you've installed a local {postgresql,mysql}-server) then the question can be skipped and everyone's happy.

Idea: Get the ["PostgreSQL"] maintainers to include a similar mechanism to the debian-sys-maint user in ["MySQL"]

-- Webserver

to manage all their variant web servers, so every package could be run on every apache.

-- Filesystem layout

-- PHP

Posible solution: You can put PHP configuration into Apache configuration files

-- Security

-- Misc (?WishList)

Posible solution: www-ressource that holds all our local/distant dbms ressouce, and web servers.

(same for databases) --> ! not all application are compatible with all the ["DBs"].