Larson, Timothy E. wrote:
Shane wrote:
On Oct 12, 2005, at 8:57 AM, Larson, Timothy E. wrote:
Then I thought, what about using my main Apache2 server as a reverse
proxy in front of slash?  I've never done this before, so I read
mod_proxy, and it made my brain hurt.  I probably need to review it
about 5 more times.  Can I run Apache1 on another machine on my LAN -
or even better, a different port on the same machine - and make it
completely transparent to users via a proxy setting in Apache2?
I don't see why you couldn't. However, why use apache2? Why not use
something like squid in reverse-proxy mode instead? I would think
squid would be 'lighter' then apache2.  

I don't know squid but already have apache2 serving a couple other
sites, and if it's already there, why add something else to the mix?

However, if mod_proxy is more of a performance hit than squid, then
maybe squid would be a better way to go.  Know of any benchmarking in
this area?

Are there any special
considerations I need to make when setting up slash this way?
Not that I'm aware of. Might be a var or two you need to set. You
don't state what version of slash you'd be running. 

Whatever is the latest and greatest at the time I get around to trying
this.  Definitely a version that includes the cleaned up HTML and CSS.
;)  I'm hoping *crosses fingers* that I'd have time to hack in a couple
features I'd really like to have for my board, so I'd want to start with
the most current stable release.


Squid works very well as an accelerator for slow, older http servers.  Details on setting up an http accelerator are here

Its actually very easy to deploy.  Even on message boards where most of the content is dynamic, caching of images and style sheets can make a significant speed improvement.