ConceptsDeploys
History and logs
Ferry keeps each deploy with its status, trigger, source, image, commit and log.
List the deploys
Terminal
$ ferry deploys node-helloID STATUS TRIGGER COMMIT CREATED DURATIONdep-fad68a5ea71b43ae9820 live upload - 7m ago 2sdep-7d2d938ff3614c238ecb canceled manual - 10m ago 0sdep-d21d077ff8464b4a9501 deactivated manual - 11m ago 2sdep-ca4bc7b5862742959b70 deploy_failed upload - 17m ago 1s✗ dep-ca4bc7b5862742959b70: instance d1c6b8 crashed (exit code 1)The command shows the 20 newest deploys. Add -n for more. The cause of each failed deploy is at the end.
Read the log of one deploy
ferry logs --deploy dep-ba5a7fce730d4061aaa7 # the full log
ferry logs --deploy dep-ba5a7fce730d4061aaa7 -f # continue while the deploy runsIn the dashboard, open the deploy from the Deploys page.
What is in the log
| Lines | From |
|---|---|
==> … | Ferry |
| Build output | Docker, during the build |
[e5725a] … | A new instance, during the health check |
GET /api/v1/deploys/{deploy_id}/logs sends the log as Server-Sent Events. See Logs & events.