Deployment Process

At Back4app Containers, we have two core concepts: the App and the Deployment.

The deployment is the process of building your code and going live with a new version/release of your App, which will also have logs and metrics. Deployments will use Back4app servers from when they start until they succeed or fail.

The deployment starts with the Building status. If it succeeds, it goes to Ready, and if there is any error, it goes to Failed. If, when the deployment starts, there is another deployment process with Building status, then this deployment goes to Queued status and will wait until the other operation finishes.

When a new deployment is successful and goes to the Ready status, the previous successful deployment goes to the Destroyed.

The Deployment statuses are:

The App means the service is running/scaling on Back4app Servers and will have running logs, metrics, domains, and settings.

After you first configure your deployment and click on the Create App button your App will be first created and start with the status Building. If the deployment fails your App will be Unavailable. If succeed will be Available. At any moment you can suspend your App then you will see the Suspended status on your Dashboard.

The deployment process runs in parallel with your App Service. That means your App will be available with the latest successful deployment while a new deployment is in progress. It is also important to note that a new release will only occur if the building process is successful, thus avoiding interruptions in your App's service.

The App statuses are: