On 8/23/05, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > The point is that serving media from Django is a Bad Idea(tm), and > one of the philosophies behind Django is that we want to make it > easier to do the right thing than to do the wrong thing.
Without CSS or JavaScript, people attempting to develop won't properly see what they're pages look like or how they behave. You may find that people separate out behaviour and presentation less (by making less use of external JavaScript or CSS) to work around the problem, which equally isn't the right thing. The development server is supposed to make development easier. It is not supposed to mimic a production environment. Put another way using your argument that you want to discourage the wrong thing, you shouldn't have the development server at all - as you don't want people running that as a production server, do you? > I'm not > going to go into why serving media from an application server is bad > unless someone really wants to discuss it; just trust me when I say > that in the long run you'll be much happier if you take the 30 > seconds to set up a static directory or subdomain to serve media from. It's not 30 seconds though, is it? Its an Apache + mod_python install. If you can do that from scratch on a windows box I'd be amazed. The development server is a _development_ server, not a production server. if people don't get that from the name, they're going to make bigger mistakes than using Django to serve media files in a production environment. -- sam http://www.magpiebrain.com/
