Jamie Heilman wrote:
This means you could effectively use pcgi with a single apache instance fronting for several zope+pcgi instances in a virtual-hosting scenario. (I used mod_pcgi2 for this purpose.) This had several seperation advantages as you can then run the zope instances as different users, ensuring your zope vhosts have no ability to cross-contaminate eachother at the zodb level, plus it was easy to define a filesystem namespace for every vhost (all of customer Foo's files go in ~foo, nice and easy).
We do all of this using mod_rewrite and mod_proxy.
just fell over if you looked at it funny. That means virtual hosting then requires either managing a battery of internal interface aliases, or a map of ports on some internal interface, or throwing all your eggs into one basket (zodb).
...and we don't do any of this, as far as I'm aware. cheers, Chris