2 ms·

Would you consider Apache appropriate for the job for someone who doesn't want to have to try six different solutions to serve their webpages? I hear what you'

• blasdel 17y ago
  You generally don't need the reverse proxies in front until you're doing something sizable (or that fits into something of size). I haven't done a project that needed them in a while! You can just use a single app server capable of processing multiple requests -- twisted.web is a solid event-driven one. If you just need to serve static pages nginx is perfect by itself. If you really need a monolithic swiss-army-knife, lighttpd is at least a pretty good implementation of a mediocre idea. I really dislike a lot of things about Rails, but I will be eternally grateful for the way their community accidentally demonstrated to the world that the ASF's crap was not the alpha and the omega of webserving. At the time the only options that people thought viable were httpd and overarchitected babel towers (lots of Java crap, WS-*, Zope, etc.).