PUBLIC_SCHEMA_URLCONF about django-tenant-schemas HOT 5 CLOSED

Hi guys, I know it's been a lot time since this discussion but I din't found much in the docs. If I setup a separate WSGI settings, how do I declare database settings? Should I use the default postgresql backend for django? How do I manage the migrations? And in this separate settings the django-tenant-shemas app would exist at all ?

from django-tenant-schemas.

I don't understand what PUBLIC_SCHEMA_URLCONF has to do with issue #43? Is the objective here just to save one query?

SHARED_APPS contain data that can be accessed from any of the tenants plus the public schema.

from django-tenant-schemas.

I don't understand what PUBLIC_SCHEMA_URLCONF has to do with issue #43?

Nothing, I just quoted things what came up there.

Is the objective here just to save one query?

Not just that, but simplify things overall. Things get very complicated if you try to use for example a CMS for the main website with data from public schema.

SHARED_APPS contain data that can be accessed from any of the tenants plus the public schema.

Currently this is not true, as you can't put auth or admin in only to SHARED_APPS.

from django-tenant-schemas.

Well, PUBLIC_SCHEMA_URLCONF is already optional, so I wouldn't like to remove it. Your idea/alternative about a separate wsgi_app is very good and would be very nice to have in the docs!

The issue with the centralized auth is another one and better discussed on #43, just so we discuss everything about it on the same place.

from django-tenant-schemas.

I add a section to the documentation about this setup then.

from django-tenant-schemas.