Troubleshooting a failed deploy on Voroa
The usual reasons a deploy fails, from a missing dependency to a wrong start command to a port your app never listens on, and how to read the log for each.
What this covers
Most failed deploys are one of a small number of problems. A dependency is missing because it was installed locally but never added to the lockfile. The build command is right on your machine and wrong on the platform, usually because of a path or an environment variable that only exists locally. The start command names a file that is not there after the build. Or the process starts fine and exits, because it never listened on the port the platform gave it. The build log tells you which of these it was: read it from the bottom, and find the first line that is an error rather than a warning.
A single troubleshooting reference covering each failure mode is not published in the Voroa docs today. The pages below cover how to read a deploy’s status and its log.