FerryDocs
Concepts

Logs & events

Ferry keeps the lines that your builds, deploys, instances and jobs write. Events tell what changed.

Edit on GitHub
Logs: lines of textEvents: what changedBuildoutput of DockerDeploysteps of FerryInstanceswhile they runJob runServereach changeDeploy logRuntime logJob logChange feed

A build writes its output into the deploy log.

1 / 5

A is the text that a program writes while it runs. Ferry keeps three logs: the deploy log, the runtime log and the job log.

You can read each log when it is complete, or follow it live.

Follow the log of a service

Terminal
ferry logs api -f

In this section

The three logsWhat each log has, and how long Ferry keeps it.Runtime logsWhat your app writes while it runs.Deploy logsThe build output and the steps of one deploy.The change feedOne stream that tells each change on the server.

Upgrade from a Ferry with no limits

After the upgrade, a container gets its limits when a deploy or a restart replaces it.

The three logs

Ferry has a deploy log, a runtime log and a job log. Each one has its own place.

On this page

Follow the log of a serviceIn this section