GuidesLanguage guides
The files Ferry looks for
Ferry chooses the runtime from the first known file at the root of your source.
Dockerfile. Runtime docker. Ferry uses your Dockerfile as it is.
1 / 7
When the runtime of a service is auto (the default), Ferry looks at the root of the source. If the service has a root directory, Ferry looks there.
The table
| File found | Runtime |
|---|---|
Dockerfile | docker: Ferry uses your Dockerfile as it is |
package.json, bun.lock or bun.lockb | node |
requirements.txt, pyproject.toml or Pipfile | python |
go.mod | go |
Cargo.toml | rust |
Gemfile | ruby |
index.html | static |
Force a runtime
ferry up hello-node --runtime node --followThe values of --runtime are auto, docker, image, node, python, go, rust, ruby and static.
See the result
The deploy log tells you what Ferry found:
==> Detected Node.js runtime
==> Generated Dockerfile.ferry for the Node.js runtimeBuilds & runtimes explains the build itself: the cache, the variables at build time and how long Ferry keeps images.