On 8/23/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 8/23/05, Sam Newman <[EMAIL PROTECTED]> wrote: > > Or more simply put, the Django web server doesn't serve your media > > (e.g. images, PNG, CSS) and there isn't a plan to (the related ticket > > is marked as WONTFIX). Which majorly blows IMHO. > > My two cents: > > I can see the value in having the development server be able to serve > media. My concern is the same as Jacob's concern -- I wouldn't want > people to use it in a production setting. > > Sam, or anybody else: How do you envision this working? > > Adrian > > -- > Adrian Holovaty > holovaty.com | djangoproject.com | chicagocrime.org
(sorry for the late response!) Firstly, why worry about this being mis-used? It's called a development server. You already say clearly "don't use this for production". Put another way, people could put their entire app into a single function if they wanted - do you stop them from doing that? Don't penalise people because you're worried about what a minority will do - if they mess up and you've done your best to warn them, it is their fault not yours. As for the dev server, all I want is something that works as well as webrick (Rails' built-in dev server) for development use - that is let me have external CSS, image and Javascript files served. Ideally, I can place these in my templates directory using relative links, but even if I had to use absolute links I'd be happy with that. -- sam http://www.magpiebrain.com/
