We are having a strange issue, we are deploying Umbraco 8 to AWS Beanstalk and whilst we can get the app deployed, and the frontend working, the backend is doing some odd things.
If i navigate to /umbraco the screen is blank and I can see that the /Application URL is pointing to the wrong place, so the following line of code in the default.cshtml file in the umbraco/views folder:
I think the issue is that the Dev Ops deploy (or some AWS config) is creating a child application in IIS:
We have tried the ResolveUrlsFromTextString setting, but this is not really a virtual directory, the app is resolving from the main URL not a virtual directory, but the Umbraco side of this is not resolving.
Has anyone got any experience getting Umbraco on AWS via Azure Devops and what they had to do pipeline/config wise, this is turning out to be a million times harder then Azure rollouts.
Deploying Umbraco to AWS Beanstalk via Azure Devops
We are having a strange issue, we are deploying Umbraco 8 to AWS Beanstalk and whilst we can get the app deployed, and the frontend working, the backend is doing some odd things.
If i navigate to /umbraco the screen is blank and I can see that the /Application URL is pointing to the wrong place, so the following line of code in the default.cshtml file in the umbraco/views folder:
Instead of generating a url like:
it is ommitting the /umbraco part and just outputting:
This obviously 404s.
I think the issue is that the Dev Ops deploy (or some AWS config) is creating a child application in IIS:
We have tried the ResolveUrlsFromTextString setting, but this is not really a virtual directory, the app is resolving from the main URL not a virtual directory, but the Umbraco side of this is not resolving.
Has anyone got any experience getting Umbraco on AWS via Azure Devops and what they had to do pipeline/config wise, this is turning out to be a million times harder then Azure rollouts.
is working on a reply...