On Sat, Sep 8, 2012 at 9:49 AM, Reginald Choudari <adnanchowdhur...@gmail.com> wrote: > Django doesn't serve files itself; it leaves that job to whichever Web > server you choose. > We recommend using a separate Web server -- i.e., one that's not also > running Django -- for serving media. Here are some good choices:
some time ago, the recommended Apache module was mod_python, which ran Python code in the same process as the media serving capabilities of Apache. that led to suboptimal use of RAM the advice was, and still is, to use different processes for media and app code, therefore a separate webserver was a good advise if you used mod_python. now, mod_python is deprecated, and mod_wsgi manages a separate process for Django. uwsgi does a similar thing. so, it's quite easy to do a very good architecture with just Apache and mod_wsgi, or just nginx and uwsgi. (there are still many other options, of course) -- Javier -- 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.
