How a deploy works on Voroa, from git push to live
What happens between a git push and a live URL: the clone, the install, the build, the start and the switch over, and what a failure at each step means.
What this covers
A deploy is a sequence of steps, and knowing the order makes a failure much easier to read. The platform is told there is new code, clones your repository at that commit, installs your dependencies, runs your build command, then starts your process. Only once the new process is up and answering does traffic move across to it; until then the previous version keeps serving. That last part is why a failed deploy usually does not take your site down. It also explains the two very different failures you will meet: a build failure, where the new code never got as far as running, and a start failure, where it built fine but the process exited or never listened.
A single page describing the full pipeline is not published in the Voroa docs today.