Skip to main content

Deploy

Our deployment system is designed for flexibility, capable of running any software that can be containerized into a Docker image.

You can also override how each environment starts its container without rebuilding the image. See Startup Command Overrides.

App types​

Before configuring deploys, choose the right entity type: Apps, Databases & Services, Functions, or Jobs. See App Types for the differences and when to use each one.

Containers​

Use more than one container so in case of crashes of your app env your app will be still available.

Read more about containers and high availability here.

Blue/green deployment​

Make sure you configure HTTP Probes, so we don't turn off your old containers while the new ones are not ready yet.

This way your deployments are going to be always zero downtime.

Storage​

We also support disk usage needs.

Scaling options​

Autoscaling automatically adjusts your warm container count based on CPU and memory utilization. Eligible Connect/BYOP environments can also use Scale to zero to park after an idle ingress window and wake on demand. Read more in the Scaling options page.

Account limits​

Ensure your account limits can adequately support your app environments and any upcoming events. To review your account limits, open Account settings from the main navigation.

Additionally, our Web App will alert you when you approach these limits, and certain actions, such as adding new containers or increasing zClouds (resources), will be restricted if your account reaches its limit.

Configurations​

Below are some configurations that you should check before deploying your app.

Block communication from other accounts​

Enable Block communication from other accounts in most cases as you want to restrict your app env to only accept connections from our Ingress and maybe from other app envs in your account.

Port​

In the App's Network section, make sure Port matches the port exposed by your Dockerfile.

Root directory​

Monorepo users should set Root directory under App Config to the relative location of the app root inside the repository.

WAF​

Enable WAF to protect your app from common attacks, such as SQL injection and XSS. Learn more in the security section on how to enable it.