On Sat, Mar 15, 2003 at 01:00:18AM +0900, Nathan Ollerenshaw wrote:
On Saturday, March 15, 2003, at 12:02 AM, Thomas Eibner wrote:
On Thu, Mar 13, 2003 at 08:27:30PM +0900, Nathan Ollerenshaw wrote:
Resending this to this list as I got no response on users list.
Currently, we are using flat config files generated by our website provisioning software to support our mass hosted customers. The reason for doing it this way, and not using the mod_vhost_alias module is because we need to be able to turn on/off CGI, PHP, Java, shtml etc on a per vhost basis. We need the power that having a distinct <VirtualHost> directive for each site gives you.
Is there a better way?
I don't know of a specific virtual host hook, but if there isn't there might be a need for it.
I guess you need to have someplace which calls your module's hook *before* the server definition gets set, and allows you to run a pre-config/post-config & followup merge for all the modules currently loaded on the first time the server-name is loaded into memory, and then pass the resulting server-config down to the rest of the hooks.
this should make it possible to allow you to do anything in your module that the plaintext v-host one could do.
--Ian
