On Oct 27, 9:18 pm, Benjamin Wohlwend <piquad...@gmail.com> wrote:
> Hi,
>
> I develop and maintain several Django sites that are all part of the
> same organization. Some of them are more of the Intranet-type (e.g.
> only for internal use), others are publicly accessible (e.g. a CMS).
> My problem is that certain data from the Intranet sites have to be
> displayed on a publicly accessible site (e.g. a list of staff members
> that is maintained on the Intranet). What's the cleanest approach to
> solve this? The potential solutions I have so far:
>
> * import the Django apps from the Intranet application into the CMS
> project and directly access the data through the ORM. In terms of
> quantity of code, this is the easiest solution (I have already working
> code). The drawback is tight coupling of projects that should by
> definition be independent of each other. And all the data has to be in
> the same database (could the multi-db branch help with this?).
>
> * use a webservice to access data from one site on another site (e.g.
> something with django-piston). This would avoid the tight coupling,
> but it would probably result in a lot of code and not so good
> performance (to display a list of staff members, the CMS would have to
> make a web request to the intranet site).
>
> * some kind of IPC. I have no experience with IPC in combination with
> Django and Python, so this would be completely new territory for me.
>
> Any ideas?
One could simply overlay URLs from one instance over another.
For example, using mod_wsgi you should be able to do:
WSGIScriptAlias / /some/path/public/site.wsgi
WSGIScriptAlias /staff-members /some/path/intranet/site.wsgi/staff-
members
I think I have second line right. The LHS has to be added to RHS so
that SCRIPT_NAME, ie., mount point still comes through as '/' for that
application. If that doesn't work, may need to do some magic and use
WSGIScriptAliasMatch in special way.
Note that this will have instance of intranet site running on same
host as public site. This may not be what you want. You may be able to
manage same thing by proxying the sub URL you are overlaying into
intranet side, but then have to deal with problem that intranet site
will generate URLs with internal intranet site host name.
Also, if you are running intranet site on same Apache, you probably be
wanting to be used mod_wsgi daemon mode for sites and delegate that
sub URL to same daemon process as intranet site is using. In effect
you have a mini proxying of a subset of URLs to internal intranet site
but done within context of mod_wsgi.
Graham
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
