Better method of serving admin media files needed

[Alex Payne <al3x@…>]

Having to manually copy the media (stylesheets, images, javascripts) used by the admin interface into one's static media directory is broken. Those hand-copied media files are quickly going to get out of sync with the latest versions from svn. Even symlinking those files into the media directory would be a better solution, and if that's the best we can do, the docs should be updated to reflect it.

[Adrian Holovaty]

Which docs need to be updated?

[hugo]

Just a hint: you can directly checkout the admin media files to your public_html or whatever the place is. That way they can be served by the webserver and won't go out of sync, at least getting in sync is easy.

[Charlax <ca.dein@…>]

It would be somewhat useful, however, to avoid such manipulations...

Here is mine :

sites_available/default :

Alias /admin_media /var/django/project/admin_media
<Location "/admin_media/">

SetHandler None

</Location>

and in settings :

ADMIN_MEDIA_PREFIX = '/admin_media/'

and :

ln -s /usr/lib/python2.4/site-packages/django/contrib/admin/media django/project/admin_media

[Michael Radziej <mir@…>]

What documentation are you talking about? docs/static_files.txt?

[Malcolm Tredinnick]

(In [4710]) Added a note about serving admin media to the alternative server setup
instructions. Refs #474.

[Malcolm Tredinnick]

The ​modpython.txt documentation mentions both symlinking and copying of the admin media files as possibilities. I've updated the fastcgi docs to refer to the same section. We don't want to be in the game of giving step-by-step server configuration instructions, since they are too varied and long. I think what we have is enough to provide people with a start and the right words for them to seek out other documentation of a more specialised nature if they require that.