FerryDocs
Architecture

Deploy pipeline

The deploy pipeline is the list of steps that the engine runs to put a new version online.

Edit on GitHub

Enqueue. The engine finds the source and stores the deploy as queued.

1 / 7

A changes a source into behind the . The source is a git commit, an uploaded folder, an image, or the image of an earlier deploy.

The runs the deploy in the background. The API call that starts it only puts it in the queue and answers 202.

This section follows one deploy through ferry-engine. For the user view, see Deploys.

Start a deploy

Terminal
ferry deploy api --follow

In this section

StatesThe state machine of a deploy.Queue and workerWhy two deploys of a service never overlap.Switch and go liveThe point after which a deploy cannot stop.When a deploy failsWhat the engine removes and what it keeps.

How ferryd starts

The ferryd program connects the other crates and starts the parts of the server in a fixed order.

States and triggers

A deploy has one state at a time, and it records the trigger that started it.

On this page

Start a deployIn this section