Preview and production
Every deployment has a target:
- Preview deployments get their own address and do not touch your production address. Pushes to non-production branches and pull requests are previews, and so is
vtx deploywithout flags. - Production deployments also update your production address. A push to the production branch, or
vtx deploy --prod, makes one.
Statuses
queued -> building -> uploading -> ready
\-> error
any step \-> canceled| Status | Meaning |
|---|---|
| Queued | Waiting for a builder. Your account can run a limited number of builds at once; see Limits. |
| Building | Installing dependencies and running the build. The log streams live. |
| Uploading | Storing the output. Files already stored are skipped. |
| Ready | Live at its address. For server apps this is only reported after the server has started and answered a request. |
| Error | The build or the start check failed. The log says where. |
| Canceled | You stopped it before it finished. |
Status only moves forward. A deployment is marked ready only after everything it needs has been stored.
Promoting
Promoting points the production address at an existing ready deployment. Nothing is rebuilt, so it is immediate.
$ vtx ls
$ vtx promote a1b2c3In the dashboard, open a deployment and choose Promote to production.
Rolling back
A rollback is a promotion of an earlier deployment. Every deployment is kept, so pick the last one that worked and promote it. The address switches straight away; the bad deployment stays available under its own address for you to investigate.
Redeploying and cancelling
Redeploy builds the same source again, for example after changing an environment variable. Cancel stops a queued or running build. Both are on the deployment page.