Hi all, > - a media files path resolver -- following a similar directory structure as > the app templates loader (<app>/media/<app> vs. <app>/templates/<app>) > - build_static -- a mangement command that'll collect media files from apps > from various locations using the media files path resolver and uses a file > storage backend to copy (or link to) the found files (file storage backend by > default), used during deployment > - an extended media file serving view that uses the media files path resolver > (in debug mode), backwards compatible replacement for > django.core.servers.basehttp.AdminMediaHandler
Couldn't agree more. But three more points: 1) Media files are linked from applications forms, so what will happen if user rename an app? Do we need some config piece for this kind of reverse? Something like app_media(app_name=None) function and APP_MEDIA? 2) More generally, we need per-application settings to handle this sort of configuration problems. One that will be autodiscovered like templates and admin. And it can contain additive variables for MEDIA, like suggested in my configuration proposal: http://groups.google.com/group/django-developers/browse_thread/thread/b7339d8577567d95 3) I've seen a solution recently that generates apache and lighttpd install scripts, found it much better than symlinks for media in production. But this one definitely needs additive variables and per-application configuration! -- Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, MSN: bu...@live.com -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
