ConceptsDeploys
Settings and the live deploy
A live deploy keeps a snapshot of its settings. A change applies at the next deploy or restart.
A deploy goes live. Ferry saves a snapshot of its image, variables, command, port, disk and limits.
1 / 4
The snapshot is why all instances of a deploy are the same. A failed deploy cannot change what the live deploy runs. A bad value in a setting cannot break the containers that run.
When a change applies
| You change | It applies |
|---|---|
Variables (ferry env set, ferry env unset) | Immediately: Ferry restarts the service. With --no-restart, Ferry only saves them. |
Build and deploy settings (ferry update) | At the next deploy. Run ferry deploy, or ferry restart if no build is necessary. |
| Memory and CPU limits | At the next deploy or restart. ferry restart is sufficient. |
The value behind a ${{…}} reference | At the next restart. |
The number of instances (ferry scale) | Immediately, with the live snapshot. |
| The command of a cron job | Immediately: Ferry restarts the cron job. |
- The reconciler, when it replaces a crashed instance.
- A scale up, and the resume of a suspended service.
- One-off jobs and cron runs.
You delete a datastore with --force and create it again with the same name. The new datastore has a new password. Run ferry restart: the service gets the new connection string.