With PowerServer 2022 R1 I could painfully deploy an App using the SnapDevelop to create the Sites folder where I set the Port Number it will use.  Then I would use the Build and Deploy the create the WWWROOT set of files so that when someone went to the mainsite/appname it would launch (from 80 initially and then use the port it was told in the IIS to use, such as port 5000). 

R1 Example:  https://webserver.somesite.com/testapp (I could have several apps that could be accessed from the main site:  

https://webserver.somesite.com/testapp1 (example port 5001)

https://webserver.somesite.com/testapp2 (example port 5002)

https://webserver.somesite.com/testapp3  (example port 5003) and so on that would route back to the port that app is supposed to run on.

With PowerServer 2022 R2, it appears to be more user friendly for deploying as its not using the SnapDevelop and the Build and Deploy to deploy 2 parts or sets of files.  But the issue I have is that now in order to launch the app I have to go the mainsite:[portnumber]/appname 

R2 Example: https://webserver.somesite.com:5000/testapp1 

https://webserver.somesite.com:5001/testapp2

https://webserver.somesite.com:5002/testapp3

https://webserver.somesite.com:5003/testapp4  which is not very user friendly or professional of an web address.

Can someone tell me how to do this in R2 to be more like R1 as for launching from port 80 and it then using the appropriate Port?  What am I missing?  Thanks!