If you are just wanting to serve out the files on the public site then you
can just copy them over from the media/uploads folder on the intranet site,
to the media/uploads folder on the public site. You can setup an cron job or
simple post_save signal on the private side that automatically copies the
files over.

Micah

On Tue, Apr 14, 2009 at 5:56 PM, shacker <shac...@birdhouse.org> wrote:

>
> We're building an intranet and a public site that share a lot of data
> but without shared views. Therefore we're building them as two
> distinct Django projects connecting to a single shared database, with
> shared apps. To reduce confusion, the contrib.admin is only enabled on
> the intranet side, not on the public side (one database, one admin
> site seemed to make sense).
>
> All is going well, but we just hit a puzzle:  After installing django-
> filebrowser and integrating it into some admin views and flat pages,
> we found that it (of course) only uploads media into media/uploads  on
> the intranet side. If you create a flat page with uploaded media and
> view it on the public site, images are broken because their URLs are /
> media/uploads.... The path is technically correct, but points to the
> file tree on the intranet side. There doesn't seem to be a way to tell
> filebrowser which filesystem to upload into. Selecting a "Site" in the
> flatpage editor doesn't communicate that info to filebrowser, of
> course.
>
> At this point I'm thinking the only way to resolve this is going to be
> to have two /admin sites after all, rather than one. Or is there
> another/better way to solve this?
>
> Thanks,
> Scot
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to