Re: Managing static content / basically handling images best practices

This is kind of an aside to your question, but I think you'll find it useful... There are two types of static media that you'll want to have served separately to your dynamic django application: * project static media * uploaded media I like to keep these two separate. My preferred way to do thi

Re: Managing static content / basically handling images best practices

Not sure if I understood the question, but here goes: Are you using the devserver on production? If you are, stop! It's perfectly fine to serve the static media via the dev server in a *DEV* environment. Here's some information: http://docs.djangoproject.com/en/dev/howto/static-files/#limiting-u

Re: Managing static content / basically handling images best practices

I typically add a config to apache to ignore my media folder and not handle it with python so that requests to /media/.* all go straight to the webserver and don't go via django. I typically have something like this sitting in my conf's: SetHandler None Options -Indexes I

Re: Managing static content / basically handling images best practices

I solved this issue by making the FileField (or ImageField) save the files into an Apache (or other web server) served directory. Though obviously this has security implications so I only do this for the password protected admin. Hope that helps cheers, Jon On Jul 15, 12:33 am, reduxdj wrote: >

Managing static content / basically handling images best practices

I want to use ImageField for users to upload static content and I need a little advice from a some django pros on how to do this in a dev enviornment. I notice the disclaimer that django dev server should not used to serve static content, or it shouldn't be. So... What's the best practice for thi