Cliff Wells <[EMAIL PROTECTED]> writes: > What I would do is this: > > In /etc/pound/pound.conf: > > ListenHTTP 1.2.3.4,80 > ListenHTTPS 1.2.3.4,443 /etc/pound/certs/turbogears.server.pem > > UrlGroup ".*" > HeadRequire Host ".*zope.server.com.*" > BackEnd 127.0.0.1,8088,1 > EndGroup > > UrlGroup ".*" > HeadRequire Host ".*turbogears.server.com.*" > BackEnd 127.0.0.1,8080,1 > EndGroup
What if both "zope.server.com" and "turbogears.server.com" were just "server.com" and the only difference on the decision was the port the user connected to (either 80 for Zope or 443 for TG)? > I'm not entirely convinced you'd need rewrite rules or even an additional > webserver (unless you are using it to serve static files). Pound was > originally developed as a Zope proxy and load balancer and includes specific > instructions on getting it set up. I'll take a look at it... If it is lighter than Apache, I might benefit from that. > I'm running TG directly behind Pound at the moment and have been running > around 30 sites on Pound + Lighttpd happily for several months now. On my test server I have a few sites, pure HTML, PHP, TG and Zope. All behind Apache. So, when I have to mix two technologies, my first choice is using Apache -- that's what I know and use here... ;-) It might not be the best, though. -- Jorge Godoy <[EMAIL PROTECTED]>
