Hi Matt,
If you do not have static serving enabled in your django application
mapping to /static/ in urls.py, then the content is being served by Apache.
What is your MaxRequestsPerChild in your apache conf?
One of the reasons production environments use a different web server
for serving static content is that wsgi applications are blocking
applications and the server blocks activity until the wsgi request is
handled. This could affect your performance for concurrent requests if
you have a single process
On 7/9/2012 3:25 AM, Matt Smith wrote:
Thx Kenneth, Rohan, Melvyn.
I've arrived at something that works:
httpd.conf:
WSGIScriptAlias /
/usr/local/django/projectName/apache/django.wsgi
Alias /static
/usr/local/django/projectName/static
So everything that's not a template lives under
/usr/local/django/projectName/static. Is this ok? Does this mean when
I link to say /static/foo.jpg in a template that foo.jpg is being
served up by apache directly, ie not handled by wsgi?
I've noticed that the site is slower to load up than before django? Is
this normal?
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
