Base solution for your next web application
Open Closed

Azure deploy and domain multitenatresolver #5353


User avatar
0
jollyticket created

Hello, I have just deployed my abp app to azure: ANGULAR: <a class="postlink" href="https://myapp-dev-client.azurewebsites.net">https://myapp-dev-client.azurewebsites.net</a> SERVER: <a class="postlink" href="https://myapp-dev-server.azurewebsites.net">https://myapp-dev-server.azurewebsites.net</a>

Can you suggest me how to set the dns mydomain.com to resolve the tenant on sub domain? I think that *.mydomain.com go to the angular app, but how can I set the DNS for the server?

It's important for me that the server app don't lose the domain multitenant resolver.

Is there a way to deploy client and server on the same app on azure like demo.aspnetzero.com?

thanks for your help


4 Answer(s)
  • User Avatar
    0
    maliming created
    Support Team

    I guess demo.aspnetzero.com might put Angular's static resources in the wwwroot directory of the Api site.

  • User Avatar
    0
    geek1913 created

    Is there a way to deploy client and server on the same app on azure like demo.aspnetzero.com?

    No. The Angular site and Host site run in separate azure web apps.

    Can you suggest me how to set the dns mydomain.com to resolve the tenant on sub domain? I think that *.mydomain.com go to the angular app, but how can I set the DNS for the server?

    This is how I did it in azure

    ANGULAR web app: *.mydomain.com = static SSL IP of ANGULAR web app mydomain.com = static SSL IP of ANGULAR web app

    SERVER web app: *.api.mydomain.com = static SSL IP of SERVER web app api.mydomain.com = static SSL IP of SERVER web app

  • User Avatar
    0
    alirizaadiyahsi created

    You can download merged project. So you can deploy only one application like demo.aspnetzero.com.

    <a class="postlink" href="https://aspnetzero.com/Documents/Development-Guide-Angular#deployment">https://aspnetzero.com/Documents/Develo ... deployment</a>

  • User Avatar
    0
    jollyticket created

    Thank you @geek1913, *.api.mydomain.com is the best solution in my scenario: I keep separate app plus multitenant resolver on sever app. Simple is better! Always