FerryDocs
ArchitectureDeploy pipeline

Switch and go live

After the health checks pass, the engine changes the routes, marks the deploy live and stops the old instances.

Edit on GitHub
Route tableOld instancesNew instanceshealthyStoredeploy: deploying

All the new instances passed the health check. After this point, the deploy cannot go back.

1 / 5

After the passes, the deploy cannot go back. A cancel after the switch gets a refusal.

The order matters

The engine marks the deploy live before it stops the old instances. If the server stops during the drain, it comes back with the new deploy.

The change of routes and the wait of 2 seconds apply to web services and static sites. Other services have no route.

The end of the log

Deploy log
==> Your service is live 🎉

The URLs of the service come after this line.

On this page