On Sat, Oct 10, 2009 at 04:10:26AM -0400, Greg Gard wrote: > hi willy, > > thanks for your efforts on this. i do see. i haven't been using > frontends at all in haproxy.cfg but i can see the benefit of doing > what you describe. mongrel though isn't the static fileserver of > choice however. currently i do a bunch of rewrites in my nginx conf to > split out the static files and serve them directly before they go to > haproxy. that puts more pressure on that machine, doing all the > static, ssl and load balancing. so i may explore the config below to > load balance static files.
if you already have nginx serve static files, you should stick to it for that purpose. It would be a bit wasted to pass through it, reach haproxy to decide where to forward the request, then have it served possibly by nginx again if you are able to do it at the first stage. > on a related note, do you have folks who are working on documentation. Not much in fact. I insist that people contributing features also add the associated doc entry but that's all. The architecture manual should be refreshed. There are complex setups using cookies that could be simplified a lot using frontends+backends. Redirects are not talked about either. > i am interested in learning more about haproxy as it is my current > hammer for whatever nail needs pounding and would like to learn more. > not a c programmer but wondered if i might be able to give back a bit > by helping out with documentation. Well, feel free to propose changes. If I can suggest one way to proceed, I think you should go through the doc and everywhere you see that an option is dedicated to a specific usage, it means that an example of such a setup should probably appear in the architecture manual. Among the things that are not currently covered : - how to split static and dynamic requests - how to regulate traffic on front of rails servers - how to politely reject excess new users while accepting previous ones - how to combine apache and haproxy for best scalability - how to use haproxy to protect apache against DoS. - how to perform non-disruptive maintenance operations - how to combine haproxy with nginx/varnish for caching - using haproxy in transparent mode for FTP, RDP, SMTP, ... - using TCP content inspection to reduce spam - using TCP content inspection to use HTTP+HTTPS+SSH on the same port - specific tuning for very high session rates - specific tuning for very high session concurrency - specific tuning for very high bandwidth - monitoring (BTW, this could be covered in a complete separate manual) As you can see, there are a lot of subjects to pick :-) Regards, Willy
