On Wed, Mar 24, 2010 at 5:36 PM, Bruce Kroeze <[email protected]> wrote:
> This is one of a huge number of reasons I discourage Apache as a production
> target for my clients. Lighttpd/Fastcgi is so much clearer and more
> debuggable as a production system. I'm simply never completely sure that
> I've "sandboxed" the Apache server properly, whereas it is quite clear with
> a separate Django daemon.
> There's just too much mystery, too much "magic" with Apache for my taste.
> Magic == hard to debug.
>
Bruce (et. al.) --
I've been using Apache/wsgi to serve dynamic content and lighttpd to
serve static. However, I think I'd like to try using lighttpd to serve
both static and dynamic content. I'm working off the brief
documentation here:
http://docs.djangoproject.com/en/1.1/howto/deployment/fastcgi/#lighttpd-setup
Do you have any other tips/hints/tricks you might like to share about
getting this configured?
Also, do you have an opinion about Cherokee?
Thanks!
--Stuart
--
You received this message because you are subscribed to the Google Groups
"Satchmo users" 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/satchmo-users?hl=en.
