On Sep 16, 7:31 pm, Brian Beck <[EMAIL PROTECTED]> wrote: > On Sep 16, 7:22 pm, Julien Phalip <[EMAIL PROTECTED]> wrote: > > > I really like the idea. However, I think there should also be a way to > > configure it to not copy to MEDIA_ROOT but to somewhere else. > > Sure - a --destination flag, defaulting to MEDIA_ROOT, would work.
There's also the issue of the application knowing where its media will be installed, so that it can access it from templates. Let's say I just did manage.py installmedia myapp and all of myapp's media got copied into MEDIA_ROOT/myapp/{css,js}/. Should I assume in my templates that the files are available at {{ MEDIA_URL }}/myapp/ {css,js}/? Or maybe there should be a settings variable, something like APP_MEDIA_URLS = { 'myapp': 'some/other/path', ... } so that the app can use {{ APP_MEDIA_URLS.myapp }}/myapp/{css,js}/. This doesn't seem like a great solution though, because there's no real "standard" for which {% blocks %} to override in an app to add css/js; maybe this configuration step should just be left to the person using the app. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---