At 12:07 PM 8/18/2006, Dirk wrote:
>waylan schrieb:
> >
> > Karen Tracey wrote:
> >> If what works for admin can't/shouldn't/won't be generalized, then
> >> maybe some documentation enhancements would help out people like me.
> >
> > See the page "How to serve static files"[1] in the docs. Then, be sure
> > to read "The big, fat disclaimer" on that page. That should answer your
> > questions for you. I would imagine the reason the ticket was marked
> > won't fix is because there is already a mechanism in place to do this.
> >
> > [1] http://www.djangoproject.com/documentation/static_files/
> >
>
>as of the writing of the email and the ticket I wasn't aware of that.

I don't think I was clear in my original post.  I had managed to get 
things working for my app using the static file filter as described 
on that page. I just wished it had been easier to find.  Dirk's note 
that he was unaware of this option before going down the path of 
generalizing the AdminMediaHandler reinforces my impression that it 
is a bit too well hidden.  Given the prominence of admin in the 
Tutorial I think it is worth pointing out to readers that admin has 
special code for serving static files like stylesheets, and that 
other apps need to use this other thing during development.  (I do 
understand that it is only for use during development, but at this 
point I don't even have a web server installed so that's exactly 
where I am.)  That's all.

>As I read the source code of django/views/static.py document_root 
>should be an absolute path. Is this correct ?

Yes, it should be an absolute path.  At least that is what is working for me.

Cheers,
Karen


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---

Reply via email to