Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multitenants #452

Open
lakano opened this issue Jul 29, 2023 · 0 comments
Open

Multitenants #452

lakano opened this issue Jul 29, 2023 · 0 comments

Comments

@lakano
Copy link
Contributor

lakano commented Jul 29, 2023

Is your feature request related to a problem? Please describe.
We have a pool of BBB servers. Each tenant could use any of theses available BBB servers, but the front-end (PILOS) should only return the associated rooms/recordings of the tenant.

Describe the solution you'd like
Scalelite detect the tenant with a subdomain name including the tenant name (eg: scalelite.domain => tenant1.scalelite.domain, tenant2.scalelite.domain )
So, we can host multiple customized version of the front-end where the BBB URL include the tenant name « tenant1.scalelite.domain »

Describe alternatives you've considered
Adding multiple front-end isn't the best idea, it's had a lot of footprint if you have a lot of tenants. Also, it's add constraint to have a subdomain for each tenant.
A better idea for me should be to have only one PILOS, and switch ALL the configuration/customization based on the current used URL.
Eg:
tenant1.com => Logo / favicon / rooms / recordings / BBB servers of « tenant1.com »
Eg: tenant2.org => Logo / favicon / rooms / recordings / BBB servers of « tenant2.org »

Additional context
Each BBB servers will share multiple tenants data, so PILOS need to filter the results based on the current tenant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant