Deploy through "Portal" link also failed with a "Resource Deployment Failure"

[SimonDarksideJ]

Tried using the "Deploy via Portal" link, which resulted in failure, detail below:

{
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
  "details": [
    {
      "code": "Conflict",
      "message": "{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\"\r\n  }\r\n}"
    }
  ]
}

*Note, this was in a brand new Azure setup with no pre-existing resources defined

[SimonDarksideJ]

Just tried again with the latest changes to the branch. Still the same result deploying to Azure. But can't seem to get much more detail than the above. Attached logs for what they are: Deployment-Microsoft.Template-20210614104233.zip

[SimonDarksideJ]

Managed to get the site to successfully deploy using updates in @yannickRe fork azuredeploy script (I suspect the newer module versions and switch to "Basic" deploy might have done it. https://github.com/YannickRe/Ghost-Azure

However, site fails to load.

[RadoslavGatev]

It used to fail because of a conflict. Web app names must be globally unique:

I will need more time to look at the whole deployment. The old handy button for azuredeploy seem to be deprecated. The ARM template needs some refactoring now, so it provides some meaningful defaults.

I'm going to leave that issue open until I am able to make it better.

[svict4]

hey @SimonDarksideJ did you manage to get the site to spin up using either @RadoslavGatev or @YannickRe deploy scripts? I also encounter an 500 error when using Yannick's.

[SimonDarksideJ]

I do have the site running using @YannickRe 's deployment, however it's not reporting security issues and requires ghost to be updated. Need a find a path to come back to @RadoslavGatev version as it is using a newer version of Ghost.

[RadoslavGatev]

Hello @svict4, We are hitting the limits of the free App Service plans when deployments get longer. Technically if you try setting up a fresh blog, there is a huge chance it will work. But if you are redeploying a newer version of Ghost it will likely need more time.

If you encounter a 503 error, it most likely means that it got stuck on database migrations. The only way to recover it is to download the db file and remove the lock.

Generally, the deployment duration can be optimized by offloading most of the work to Azure pipelines/GitHub actions that can download the npm packages and leave just the database migrations to run on Kudu for example. However, that would make it more difficult for people to get started deploying Ghost on App Service...