deploy.sh | universal deployment script | Continuous Deployment library

You can use ARM templates or Azure PowerShell to run multiple scripts on a single custom script extension.

I tested the same using Azure PowerShell with the below script :

The problem was that the server was listening on localhost inside the container (source). I had to change appsettings.json to make it listen on 0.0.0.0:

According to the docs, Platform hooks need to be executable. Of note, this means they need to be executable according to git, because that's what Elastic Beanstalk uses to deploy.

You can check if they are executable via git ls-files -s .platform; you should see 100755 before any shell files in the output of this command. If you see 100644 before any of your shell files, run git add --chmod=+x -- .platform/*/*/*.sh to make them executable.

The short answer is to redirect the standard file descriptors (standard input, output, and error) for the script's java command like this:

From the error about a missing dependency, I think you forgot to run yarn

I've updated the instructions to include this as step #2

• On Linux, it's important that any bash deployment scripts that get run have Unix line endings (LF) and not Windows line endings (CRLF).

• Kuduscript will generate scripts with platform-appropriate line endings, but if those scripts are modified, or if you provide your own custom deployment scripts, it's important to make sure that your editor doesn't change the line endings.

• If something seems off with your deployment script, you can always use the Kudu console to delete the contents of /home/site/deployments/tools.

• This is the directory where Kudu caches kuduscript-generated deployment scripts. On the next deployment, the script will be regenerated.

• The error you're currently seeing is a Kudu issue with running node/npm for deployments.

• The easiest and fastest resolution for what you are currently seeing is to specify engines.node in your package.json.

Error: EISDIR: illegal operation on a directory, open '/home/site/wwwroot/wwwroot/Identity/lib/bootstrap/LICENSE'

EISDIR stands for "Error, Is Directory". This means that NPM is trying to do something to a file but it is a directory. In your case, NPM is trying to "read" a file which is a directory. Since the operation cannot be done the error is thrown.

Three things to make sure here

1. Make sure the file exists. If it does not, you need to create it. (If NPM depends on any specific information in the file, you will need to have that information there).
2. Make sure it is in fact a file and not a directory.
3. It has the right permissions. You can change the file to have all permissions with "sudo chmod 777 FILE_NAME".

Note: You are giving Read, Write and Execute permissions to every one on that file.

This error Error - Changes committed to remote repository but deployment to website failed. occurs when you push a local branch that doesn't match the app deployment branch on 'azure'.

• To resolve this error, Verify that the current branch is master. To change the default branch, use DEPLOYMENT_BRANCH application setting (refer to Change deployment branch).

You are also getting Trying to access array offset on value of type null error and that is failing composer.

• To resolve this error, you need to updater the composer.

The issue is related to your account being suspended. To reinstate the billing account is to update the payment method and settle the outstanding balance and reopen the account so you may use the project link in it.

To update the payment method, kindly refer to the steps on this page.

To reopen the billing account, kindly refer to the steps on this page.

Aha. Found it. I was missing ARG in docker file