On Mon, May 22, 2006 at 10:58:22AM -0500, Adrian Holovaty <[EMAIL PROTECTED]>
wrote:
>
> On 5/19/06, Josh Trutwin <[EMAIL PROTECTED]> wrote:
> > According to the docs, serving the css in the admin is best done
> > via:
> >
> > 1. Create a symbolic link to the admin media files from within your
> > document root. This way, all of your Django-related files -- code
> > and templates -- stay in one place, and you'll still be able to svn
> > update your code to get the latest admin templates, if they change.
> >
> > 2. Or, copy the admin media files so that they live within your
> > Apache document root.
> >
> > Wouldn't it be easier to do this in httpd.conf?
> >
> > Alias /media
> > /your/path/to/python/lib/python2.4/site-packages/django/contrib/admin/media
That's more or less what I do, except I'm using the debian packages that
I created that actually put the media in
/usr/share/python-django/contrib/admin/media, there's a symlink in the
package so that the runserver also works :)
I try to keep the packages up to date, incase anyone is interested, the
current set of packages are available from:
deb http://www.sommitrealweird.co.uk/debian/ sarge django
or, if you're running sid, just replace sarge with sid ;)
I've just noticed that flup is about to enter the debian unstable
archive, which is nice. I currently use flup to serve a (small) django
site that a lug uses, using the apache2 scgi module, seems to be a nice
way to run it so far.
Cheers,
Brett.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" 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-users
-~----------~----~----~----~------~----~------~--~---
