Alec, Mezzanine is using standard django.contrib.sites. Nothing special there. The main issue with the sites framework is that each site runs using a separate process and settings, so the resources can add up depending on how you setup the stack, and managing the tenants becomes the issue as they grow in number. Apache with modwsgi using self destructing daemons is the best solution here.
Until https://code.djangoproject.com/ticket/15089 is resolved IMHO django-hosts is currently the best lightweight solution for multi- tenancy requirements in django, but not useful with a project like Mezzanine I'm afraid. https://github.com/ennio/django-hosts cheers, Brett On May 9, 1:02 pm, Alec Taylor <alec.tayl...@gmail.com> wrote: > Dear Django-developers, > > I've been using Django for a few months now, and recently—for > different projects—started using the web-framework: web2py[1], and the > Django project: mezzanine[2]. > > Both advertise as being multi-tenant solutions[3][4]. > > Would it be possible to extend Django to meet this use-case? — Or have > I overlooked something and is this possible already? > > Thanks for all information, > > Alec Taylor > > [1]http://www.web2py.com/ > [2]http://mezzanine.jupo.org/ > [3]https://groups.google.com/forum/#!topic/mezzanine-users/4XPe5MaD4Fw > [4] PyCon 2012 > talk:http://youtu.be/M5IPlMe83yI?t=5m32shttp://dl.dropbox.com/u/18065445/Slides/PySFTalkSlides.pdf(slide42, > see yt for more info) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
