You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: