I'm getting ready to setup a site that could potentially have quite a bit of traffic (at least in bursts). I've already decided I want to use nginx as my front-end/reverse-proxy server. However, I'm not sure what my setup should be beyond that.
I've already done a successful test simply using nginx to proxy to a standard paster/virtualenv setup. Would it be faster/more efficient to use Apache + modwsgi, as from what I'm reading Apache is multi- threaded and paster isn't? I'm also unsure as to how that works. It appears when using Apache+modwsgi it replaces paster, or do you still have to run paster too, thus effectively running 3 different services? My current assumption is if there's alot of cacheable content Paster + nginx would be just fine, but if I'm gonna have a bunch of unique, user specific requests I'd probably want to use Apache/WSGI + nginx. Am I right? And come someone with more experience please expound on this? thanks! - Derick PS: We really really really need some guides/faqs/how-tos in the new TG2 docs about such topics (most of the info I've found came from mailing lists or the Pylons site) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
