Getting startedFerry and Render
Inside Ferry
All of Ferry runs in one process, ferryd. Docker runs your apps on the same machine.
A request goes to the proxy. The proxy sends it to the correct container.
1 / 5
The parts of ferryd
| Part | Work |
|---|---|
ferry-proxy | The public proxy: routes by Host header, and TLS |
ferry-api | REST, Server-Sent Events and webhooks, for the dashboard and the CLI |
ferry-engine | Deploys, the reconciler, cron and datastores |
ferry-build | git and docker build |
| SQLite | The desired state, in ferry.db |
What the engine does
- A deploy. The engine clones the repository, or unpacks an upload. It detects the runtime and builds an image.
- The switch. The engine starts new containers next to the old containers and tests their health. Then it moves the proxy to them in one step. It drains and stops the old containers. See The steps of a deploy.
- A repair. The reconciler replaces each container that crashed. It also keeps the number of instances correct and updates the routes.
Read more in Architecture.