thanks for the detailed and concise reply! i have two more question though: 1. my apache server on port 80 serves both a normal site (php) and the django files. i would like to keep my normal site on port 80. is there a way to keep it that way? as far as i understand the two servers must be running on different ports. 2. is there any effect of the apache-does-all on the system except performance? thanks itay
On Wed, Jan 20, 2010 at 5:40 PM, Javier Guerra <[email protected]> wrote: > On Wed, Jan 20, 2010 at 10:24 AM, Itay Donenhirsch <[email protected]> wrote: >> the question is - why use nginx at all? why not let apache serve the >> static files as well? what's escaping me? > > the mod_python module runs Django (or any python code) in the same > process than the rest of apache. that means that any apache thread > would do both static files _and_ Djando apps, therefore any internal > caching done by Apache impacts negatively on the python space, and > viceversa. It's better to have some threads dedicated to static > files, and others to app processing. using any out-of-sever-space > strategy (two webservers, FastCGI, mod_wsgi in daemon mode, etc) > achieves that. > > -- > Javier > > -- > You received this message because you are subscribed to the Google Groups > "Django 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/django-users?hl=en. > > > >
-- You received this message because you are subscribed to the Google Groups "Django 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/django-users?hl=en.
