DocsConfiguration

Deployments

How builds, health checks and rollbacks work.

Configuration 4 min read

Every deployment runs through five stages. If any stage fails, the previous version keeps running and your users notice nothing.

  1. 1

    Prepare environment

    A clean, isolated container is created with your selected runtime.
  2. 2

    Pull source

    We fetch the exact commit, archive or image you deployed.
  3. 3

    Install dependencies

    Packages are installed from your lockfile. Caches are reused between deploys to keep this fast.
  4. 4

    Start service

    Your start command runs with your environment variables injected.
  5. 5

    Health check

    We wait for the process to stay up (and for web services, to answer on its port) before switching traffic.

Rolling back

Open the Deployments tab of a service and click Redeploy on any previous successful deployment. It is live within seconds because the build is already cached.

Automatic deploys

When a service is connected to GitHub, every push to the selected branch starts a new deployment. You can pause automatic deploys from the service settings during sensitive periods.

Was this article helpful?