I wanted to point out that Mezzanine doesn't actually just use django.contrib.sites. Mezzanine uses django.contrib.sites and thread locals. The way it is set up example1.com and example2.com can both be driven by the exact same django instance but have different content. The third paragraph in the first post of this thread explains a bit more about how it works: http://groups.google.com/group/mezzanine-users/browse_thread/thread/e173dee4c683e05c
On May 9, 8:15 pm, Brett H <brett.hay...@gmail.com> wrote: > 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. > > Untilhttps://code.djangoproject.com/ticket/15089is 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/S..., > > 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.
