Skip to content
spredrstatus
sign inget started
Documentation index
How it works

A deploy

Every push to your service’s branch is a new release. Your customers move to it only when it is healthy: they never see a broken deploy.

time →pushbuildit starts, apartit answers /healthlivev14what was liveserving your customersfinishes, stopsv15your pushbuilt and signedstarting200 OKserving your customerscustomers move over only nowif it doesn't answer: v14 keeps serving and the deploy shows as failed
v14v15time ↓serving your customerspushbuilt and signedstarting, apartit answers /healthcustomers move over only nowlivestopsif it doesn't answer: v14 keepsserving, the deploy shows as failed

spredr deploy shows you each step as it happens, and ends when the release is live or has failed.

you start itWith a push to the branch, or with spredr deploy for the latest commit.
you follow itspredr deploy shows you the build as it happens and waits until it is live or fails.
if it failsThe previous release stays live. spredr build gives you the build log and spredr logs --stream deploy what happened at start.
if you regret itspredr rollback goes back to an earlier release in seconds, without building again.
terminal
$spredr deploy
$spredr build
$spredr logs --stream deploy
$spredr rollback v14
thenReleasesGoing back without building again.useSettingsPort, health path and memory.