On 29 Jun., 18:41, "Ariel Mauricio Nunez Gomez" <[EMAIL PROTECTED]> wrote: > 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.
Users are authenticated with ldap. So there are identical credentials for django and moodle (and our other web apps). > It is very easy to write django models to get access to moodle functions. Up to now I don't havy any experience with moodle. I'm hoping I don't have to become an expert on moodle internals just to "embed" it into my django app, as I fear it to be a rather complex system - and becoming an expert to be a very time consuming task... Hence my idea of a rather generic approach to the problem. ;-) > 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. I don't know nginx... Does it give us more options than Apache? Our setup is as follows: We have Apache2 running as the only "visible" server. It serves PHP and static files and it acts as proxy for Django and Zope2 running on the same machine. But my suggested proxy approach even would allow for "django-embedded" php/zope apps running on other machines. It would give us rather flexible options... if it'd work. ;-) Thanks for your feedback! -Stephan --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
