Getting startedQuickstart
If a deploy fails
A deploy that fails does not replace the live version.
Ferry starts a new instance. The live instance answers the requests.
1 / 3
Try it
Deploy with a start command that crashes.
Terminal
$ ferry up --start-cmd "node crash.js" --followUpdated 'node-hello': start command…09:37:33 [d1c6b8] Error: Cannot find module '/app/crash.js'…09:37:34 ==> Removing 1 new instance(s)09:37:34 ==> Deploy failed: instance d1c6b8 crashed (exit code 1)Deploy dep-ca4bc7b5862742959b70 failed (deploy_failed): instance d1c6b8 crashed (exit code 1)The command stops with exit code 1. The previous deploy continues to answer.
If an instance crashes during the health check, the log also shows the last 50 lines of its output.
Repair it
Remove the setting and deploy again.
ferry up --start-cmd "" --followExamples: a health check that gets no answer in time, or a port that another program uses. See Troubleshooting.