For whatever reason i can not determine, apart from the 'stupid' errors that keep sneaking up after i attempt to access media files (files submitted through the user) during my Django application, why I simply can't server media files!

During this situation, all I would like for instance would be to have the ability to offer images towards the front which have been submitted. My up properly serves static files via /static/, however when I attempt for everyone my /site_media/ files hell breaks loose! What could I do wrong?

So, after recognizing that Django wasn't basically crafted to really handle media files, I made the decision to turn to using Apache through the suggested mod_python option enjoy it is suggested to complete being produced. But I have never carried this out before, and am wondering whether this really is worthwhile around the development server.

Well, I understand eventually I must go lower this path after i go production, and thus will still need to learn to do that, but do you know the benefits and drawbacks with this route around the development server?

It's surely a professional because the django serves the demands faster without needing to cope with the media.

A disadvantage is the fact that, assuming you edit the media, you have to also restart the apache, for that media to refresh.

update according to your comment:

You are able to of-course easily get it done. One easy way I practice this really is, using the nginx and symlinking the media folder into nginx sites-enabled and run nginx on port 80 (or other).

You are able to set the MEDIA_URL inside your configurations, in which you point it towards the url using the appropriate port.

First, mod_python is not suggested. Actually, it's particularly suggested against. Use mod_wsgi rather.

Next, we've no way possible of telling what you are doing wrong when serving static media through the dev server, since you have given no code or particulars of the setup.

Finally, there's pointless the reason why you can't use Apache - as well as, a light-weight server for example nginx - and point it at the static directory only. Then, set STATIC_URL inside your towards the address offered with that server. It does not matter what port it's on while you are in development.