Hi Eduardo,
[adding Stephen McDonald to CC]
Il 29/04/2014 21:43, Eduardo Rivas ha scritto:
Mezzanine, a Django based CMS, has true multi tenancy. I've used it and
works great. However, it's clear it's not something that should be in
Django's core, for the reasons other have stated. I'm just bringing it
up in case OP is still looking for something like this for his projects;
not trying to restart the debate.
http://mezzanine.jupo.org/docs/multi-tenancy.html
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/utils/sites.py#L12
Thanks for the info, was not aware of that. The functionality looks the
same as the patch below [1] attached to #15089 except they save the
site_id for the request in an external cache. It looks like if the patch
goes in they could leverage get_current_site(request) with empty
settings.SITE_ID just fine.
Let me say again the what i'm pushing to have in django is to have
django.contrib.sites return a Site based on the request instead of the
one hardcoded in settings.SITE_ID.
thanks,
riccardo
[1]
https://code.djangoproject.com/attachment/ticket/15089/0001-Make-settings.SITE_ID-optional-for-django.contrib.si.patch
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/5360A829.9000609%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
