which can be shipped out to customer via
Web Deploy from the
Target platform dropdown menu.
A deploy build will do the following:
npm installwill run to install any dependencies you have.
npm run buildwill run if a
buildscript is detected in the
scriptssection of your
package.jsonin order to build the web assets for your application.
wwwdirectory with your built application will be stored and made available for live updates via
- You can find the history and status of your deploy builds in the side menu under
Each account plan has a defined maximum amount of concurrent builds allowed (see Plans Details). This limit is enforced at the account level across different apps.
When you trigger a build, in the Appflow Dashboard you will notice that a build can have different statuses before it is processed:
- Queued: this means that your build is queued for the next available runner. Usually your build should not be in this state for more than few seconds.
- Pending: this means that you have reached your concurrent build limit and your build will continue when your current builds are completed.
After the build starts to be processed the statuses are:
- Running: the build is currently being processed. You can read the logs in the build details.
- Successful: the build terminated in a correct state.
- Failed: the build terminated in an incorrect state.
More concurrent builds can be added to your plan. If you have a Starter or Starter + Add-on plan, you can get more builds by upgrading your plan.
If you have a Growth or Scale plan, please contact us.