Sign up ×  Which of Lighttpd and Nginx is, basing on your
experience, better suited for Django? I've used both and can
hardly notice any difference at all, they just work fine... Are
there any use cases when one of them acts much better than the
other? When answering please take in account both simplicity of
configuration and efficiency.  My usual setup is to have a
separate Django FCGI process (like in ./ runfcgi daemonize=false
port=8098 host= launched via daemontools or an init.d script and
lighty/nginx acting as a reverse proxy.  Oh, and if you feel
some other http server is much better for Django than Lighty and
Nginx, please don't hesitate to share your thoughts.
share|improve this question  closed as primarily opinion-based
by HopelessN00b Dec 5 '14 at 11:45   If a fastcgi service dies,
daemontools supervise will restart it within five seconds, so
the service is back up. But you still have a tiny lag of
downtime there. In my deployment I found fastcgi to be fragile
stopping unexpectedly under mild pre