#15089: contrib.sites and multitenancy
-------------------------------------+-------------------------------------
Reporter: legutierr | Owner: nobody
Type: New feature | Status: new
Component: contrib.sites | Version:
Severity: Normal | Resolution:
Keywords: | Triage Stage: Design
Has patch: 1 | decision needed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 1
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by apollo13):
* cc: florian+django@… (added)
* version: 1.3-beta =>
Comment:
I would keep ''get_current_site'' as is (eg don't perform any magic
regarding SITE_ID) and just add a setting to allow users to add their own
backend to resolve the current site. Looking up a Site object based on the
request is a twoliner then.
Is there anything else which needs to be done to get this ticket rolling
again?
--
Ticket URL: <https://code.djangoproject.com/ticket/15089#comment:30>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en.
