Releases

How your code becomes an image, what starts a new build, and how to undo one.

Every deploy goes through three steps. They apply only to sources Deplo builds: a Docker image app has no build settings, and neither a Docker image nor a Compose app can roll back.

Build settings decide how your code becomes an image: the builder, its commands, and the port the app listens on. Most apps never need to change them. Learn more ->

Automatic deployments decide what starts a new build: a push to the branch, a new tag, or a call to a deploy hook URL. Learn more ->

Rollbacks bring back an image that already worked, in seconds and without a rebuild. Past the kept builds, an app from a repository rebuilds the old commit instead. A rollback does not stop future deploys, so turn off deploy on push first if the branch itself is broken. Learn more ->

Did this page help you?

Git connections

Connect a GitLab, Bitbucket or Gitea host, on their cloud or on your own instance.

Build settings

How your code becomes a container image, which builder runs and which port it uses.