Open SuperDJ opened 2 months ago
This is extremely useful and what I'm looking for, I'm going to try to experiment myself and hack a bit building several tenants, have you tried this with the current setup?
@killua99 no, at the moment I haven't tried anything yet. At the moment I could think of two possible solution for now.
A way to make something like this possible would be for example with a "level" of tenancy or relations. Then when using the tenant()
and tenancy()
methods add a "level" parameter. It could then look like tenant(0)
for the main tenant and tenant(1)
and so on for lower level tenants.
I'd need a very specific example of how this would be structured (including identification, database structure, etc) to consider this.
Description
Would like to make it possible to have some sort of sub tenant. For example I make a paas app for my customers/ tenants (main tenants). These tenants have their own customers/ tenants (sub tenants) that would also use the app. Would be nice to make it possible to identify the main tenants by subdomain and the sub tenants by path. The main tenants could each have their own database while the sub tenants are in the main tenants database.
Why this should be added