On Tue, 2003-11-11 at 18:34, Chris Grau wrote: > Is there a particular reason you've chosen to generate many VirtualHost > directives in your configuration file? Have you tried mod_vhost_alias? > It sounds like a perfect fit for you.
Yes - namely that this will be a migration from an existing environment making very heavy use of suexec, and mod_vhost_alias gives me no control over user/group settings. To expand a little: the present system uses many servers where sites are served from a single location. Loss of a server loses all sites on that server. I'd like to move to a clustered environment, load-balanced, with a filestore backending the whole thing; loss of a server then only results in increased load across the cluster, and is much more scalable long term. Each site has a specific username which scripts run as, and it will not be possible to change this behaviour. I want to be able to store vhost configs in a database and pull them in "on the fly" when Apache starts, since the performance hit will then not result in a server being disk-bound as it enumerates the config file(s). If, as previously stated, this implies working with the "old" mod_perl/Apache branches, so be it. I cannot really see any other way of doing this, unless I start to make massive use of mod_rewrite aswell! Graeme -- Graeme Fowler <[EMAIL PROTECTED]> -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
