There is documentation that talks about tenancy and how to implement in general but I am not sure what a client solution looks like
- When tenant goes to tenant.mysite.com, is it supposed to show the "Current tenant: Not selected (Change)" development option?
- How does the Application know what tenants are available and which subdomains are 'invalid' - also, where would I set up a route when a user tries to hit an invalid subdomain
- Do all tenants get sent to a single hosted AngularUI solution?
- When using a solution like a VM with IIS: Is it supposed to be a single directory for the AngularUI, a single DIR for API, and then Multiple SQL Database Connection strings per tenant?
- How exactly is the model expected to work with Multi-tenant in IIS?
- Do I have to add a site on IIS per tenant?
2 Answer(s)
-
0
When tenant goes to tenant.mysite.com, is it supposed to show the "Current tenant: Not selected (Change)" development option?
In the development time, you don't need to use subdomains for tenants for a simpler development experience. When you do like that, a 'tenant switch' dialog is used to manually switch between tenants.
https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Overview-Angular#multi-tenancy
How does the Application know what tenants are available and which subdomains are 'invalid' - also, where would I set up a route when a user tries to hit an invalid subdomain
The application will check if the tenant exists based on the subdomain. If not, Host is used by default.
Do all tenants get sent to a single hosted AngularUI solution?
Yes
When using a solution like a VM with IIS: Is it supposed to be a single directory for the AngularUI, a single DIR for API, and then Multiple SQL Database Connection strings per tenant?
You can merging Client and Server Solutions Client and Server solutions are designed to work separately by default. If you want to work on a single Visual Studio solution, you can select "Single Solution" checkbox while downloading your project. https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Getting-Started-Angular#merging-client-and-server-solutions https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Getting-Started-Angular-Merged
How exactly is the model expected to work with Multi-tenant in IIS? Do I have to add a site on IIS per tenant?
Only need a website. https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Overview-Angular#multi-tenancy
-
0
In the development time...
Ok, but I am attempting to push to production. All the options and settings that I've seen for build have been specific for a Production environment. Where exactly am I supposed to switch something to tell the application that this is production - since all the places that I saw should have told the application this is Production yet the option is still showing up.
Is there a setting that would delete that from being on the login page or is this a manual edit that must be made on the application when we are ready for production?
I noticed that if I setup a new tenant/user, when validating the user it emails a link for verification. The link sends you to a Tenant.mywebsite.com. What I'm having an issue understanding is the tenant option is already selected when I use that link and it does indeed sign me into that tenant
When I use a new browser to go directly to tenant.mywebsite.com, it only ever sends me to the host tenant
Based on your description of how tenant routing works, it seems to not be able to recognize the tenant in the browser and always sends me to host.
There are no errors in the log and the network logs do indeed show that tenant.mysite.com was hit Where in the application does it identify which tenant it should be routing to?
If log is telling me that I’m hitting the right tenant and browser always sends me to host - is this a bug with the application or if not, can you direct me to identify where it might be failing?
2020-01-07 edit: It looks like there was an additional issue that was causing my confusion. The account.component.html was modified by dev and due to that error it caused the issues mentioned
