Hm, that's not sufficiently better than just supplying a new middleware to
be honest. The sort of hooks I prefer are where you can subclass and
improve what we ship with and give the user a new, non-fragile one, whereas
that just sounds like it's injecting a function in.
Honestly, given Channels i
I know this is not general, but maybe `get_user` could accept an optional
function as second parameter, so that the function could wrap the inner
content of the current `get_user`. django-tenants provides a regular
middleware, but I think the async breaks any attempt to handle this through
a ch
What sort of hook would you be imagining? The DB connection stuff is deep
inside Django itself, rather than in Channels, so I'm not sure what
sensible top-level thing we could provide that would make sense.
Andrew
On Tue, Nov 13, 2018 at 2:16 PM wrote:
> Django-tenants is a package to provide m
Django-tenants is a package to provide multi-tenancy in Django through
Postgres schemas (https://github.com/tomturner/django-tenants/)
Django-tenants relies on setting the schema on the connection in order to
make queries to the right Postgres schema. When you want to secure your
consumers with
4 matches
Mail list logo
