FerryDocs
Concepts

Builds & runtimes

A build makes a Docker image from your code. Ferry finds the language and writes the Dockerfile for you.

Edit on GitHub
Your codegit or uploadRuntimeDockerfiledocker buildImage

Ferry gets your code from git or from an upload.

1 / 5

A makes a Docker from your code. Each deploy of a git service or an upload service builds an image.

Ferry finds the of your code: Node.js, Python, Go, Rust, Ruby or static files. Then it writes the for you. Thus you can deploy with no knowledge of Docker.

For full control, commit your own Dockerfile. Ferry then uses it.

A service that deploys a prebuilt image has no build.

Start a build

Terminal
ferry deploy api --follow

The build is the first step of a deploy. --follow shows its output.

In this section

The build stepFrom the source to an image, in five steps.DetectionThe files that tell Ferry the runtime.Generated DockerfilesWhat Ferry writes for each language.Start commandHow Ferry knows the command that starts your app.

History and logs

Ferry keeps each deploy with its status, trigger, source, image, commit and log.

The build step

The build is the first step of a deploy. It goes from the source to an image in five steps.

On this page

Start a buildIn this section