Non Localhost Endpoints for Multi-Tenancy Support #7310
Unanswered
rburnham-def
asked this question in
Q&A
Replies: 1 comment
-
See #4319 for the longer discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We're setting up Multi Tenancy support in our app. At the moment for Dev we would manually update our host files to include a couple of different tenants (client1.myapp.local, client2.myapp.local). We read the host header on each request to direct it to the correct DB based on a cache list of tenants we have. In dev we initialise this from a tenants.json file.
So in the Aspire config is it possible to be able to read the tenants in the tenant.json file and then expose a none localhost endpoint for each one. It would be nice if we can automate updating the host file as well but that's another problem. Or is it still technically the same endpoint because the ports will be the same? It would be nice if we could list the configured tenant's url in endpoints instead of localhost as this won't map to a tenant.
Beta Was this translation helpful? Give feedback.
All reactions