I have 'integrated' django and moodle in the past. For authentication I would suggest using a single source (In my case is imap auth using google apps for your domain) and both moodle and django validate credentials against it. It is very easy to write django models to get access to moodle functions. However I wouldn't recommend the django-app as proxy approach you suggest, better to write some matching moodle themes and css for django apps and use something like nginx to do the routing.
Best, Ariel. On Sun, Jun 29, 2008 at 11:31 AM, spacetaxi <[EMAIL PROTECTED]> wrote: > > Hello djangonauts, > > maybe someone of you has a good solution for the following scenario: > > We have several rather complex web applications (partly php-based, > partly zope2-based) and I'd like to integrate them into one django- > based front-end. New apps will be implemented with django, but we > definitely need these "legacy" (php/zope2) apps to be available to the > user within *one* front-end. Ideally the different apps should look > like they actually were *one* app. (By the way, one of the php-based > apps is Moodle (www.moodle.org).) > > This is my vision: After an user has logged into the (to-be-developed) > django site, he get's some kind of "menu bar" (based on yahoo's yui) > on the top of the screen. Every menu item selects a different web > application, which may be django-based, php-based or zope2-based. The > selected application will be shown below the menu bar, so the user can > use the menu-bar to switch between the different web apps. > > Do you have an idea, how this could be implemented? > > Currently, I'm thinking about implementing some kind of http-proxy > within my django-app, so django would forward the incoming requests > (get/post) to the particular application. When receiving the response, > django could modify the html source so the content gets embedded into > my common page template (with the menu bar at the top of the page). > Additionally I'd implement a "authentication bridge" between the > different apps to share the login information with django. > > Is this a reasonable way to do it? Or do you have a better approach? > Thank in advance for any hint! > > -Stephan > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
