Am 26.10.2006 um 16:21 schrieb orestis:
>
>>> (1) to use the dev server
>>> (2) no changes when moving to production
>>> (3) to have core and non-core content served out of the
>>> ADMIN_MEDIA_PREFIX prefix.
>>
>> 1 and 2 is true (especially 2).
>> 3 not ... I don´t care serving admin_media
> > (1) to use the dev server
> > (2) no changes when moving to production
> > (3) to have core and non-core content served out of the
> > ADMIN_MEDIA_PREFIX prefix.
>
> 1 and 2 is true (especially 2).
> 3 not ... I don´t care serving admin_media with a different prefix.
>
Why don't you follow
thanks everybody for the patience and the detailed answers.
using --adminmedia might be a solution. I can´t check that, because
on that specific server we´re on 0.95.
guess I´m giving up on this issue and stay with the symlink from /
django/contrib/admin/media/.
still, some notes below.
Am
On Wed, 2006-10-25 at 14:58 +0200, patrickk wrote:
> thanks malcolm, I think we´re getting closer ...
>
> Am 25.10.2006 um 14:42 schrieb Malcolm Tredinnick:
>
> >
> > On Wed, 2006-10-25 at 14:13 +0200, patrickk wrote:
> >> sorry for being a pain in the neck, but we´re about to go online with
>
There is an option to manage.py
--adminmedia=ADMIN_MEDIA_PATH
that might just do what you need.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
Look, there are two distinct things here:
a) The admin media, which physically resides on
django/contrib/admin/media and which the dev-server serves
automagically and
b) Your own media, which you are responsible of serving, either in
production or development mode
Here's what I do:
For admin
thanks malcolm, I think we´re getting closer ...
Am 25.10.2006 um 14:42 schrieb Malcolm Tredinnick:
>
> On Wed, 2006-10-25 at 14:13 +0200, patrickk wrote:
>> sorry for being a pain in the neck, but we´re about to go online with
>> our site and I desperately need to solve this problem.
>
> You
On Wed, 2006-10-25 at 14:13 +0200, patrickk wrote:
> sorry for being a pain in the neck, but we´re about to go online with
> our site and I desperately need to solve this problem.
You already mentioned that you have solved it using lighttpd (or, at
least, that's what you seem to have
sorry for being a pain in the neck, but we´re about to go online with
our site and I desperately need to solve this problem.
solutions I had so far:
1. hardcoding media-urls incl. the host (not nice)
2. symlink from /django/contrib/media/ to /media/ (problem with
django-updates)
short
Am 25.10.2006 um 10:41 schrieb orestis:
>
> I think you have confused some concepts. /django/contrib/admin/media/
> hosts the admin media files.
>
> You mention content uploaded by users... In what directory is this put
> under ?
/media/uploads/
>
> Static files are documented here:
>
I think you have confused some concepts. /django/contrib/admin/media/
hosts the admin media files.
You mention content uploaded by users... In what directory is this put
under ?
Static files are documented here:
http://www.djangoproject.com/documentation/static_files/
Am 24.10.2006 um 19:11 schrieb orestis:
>
> You mention dev-server, yet you talk about apache and lighttpd.
>
> If running the dev-server, you shouldn't do anything, since it figures
> out itself how to serve files.
yes, but it looks for media-files in django/contrib/admin/media/ ...
I´d
You mention dev-server, yet you talk about apache and lighttpd.
If running the dev-server, you shouldn't do anything, since it figures
out itself how to serve files.
If you're running apache, either with mod_python or with mod_fcgi, you
should just create a link to the /foo/bar/admin/media
13 matches
Mail list logo
