Deployments
A deployment is one immutable version of your site. HostEdge never changes a deployment after it is built; going live, rolling back and promoting a preview only move routes.
Statuses#
| Status | Meaning |
|---|---|
| Queued | Waiting for a builder. Usually a second or two. |
| Building | Installing dependencies and running your build command (skipped for static uploads). |
| Deploying | Uploading assets and the Worker script to the edge. |
| Ready | Live at its own URL, and at the production URL if it is a production deployment. |
| Failed | Something went wrong. The log says what, in plain words, and what to change. |
| Canceled | You stopped it before it finished. |
New free accounts' deployments can also show In review: the files are uploaded but not reachable until a person checks them. See Limits and fair use.
Uploads#
Uploads are content-addressed. Each file is hashed in your browser (or by the CLI), HostEdge answers with the hashes it hasn't seen in your workspace, and only those are sent. Re-deploying a site where one file changed uploads one file.
HostEdge refuses symbolic links, paths that escape the folder, and files that look like secrets (.env, private keys). .git, node_modules and other tool folders are skipped.
Builds#
If the project has a build command, it runs in an isolated container with your environment variables for that environment. The output folder (for example dist) is what gets deployed. Without a build command the uploaded files are deployed as they are.
When a deployment fails#
A failed deployment shows What went wrong above the build log: a short title, the likely cause, numbered fixes in order of likelihood and the settings to check, with links to them. It reads the failure reason and the end of the log, so it covers the usual suspects: a missing package, an out-of-date lockfile, an output directory that does not match your build, a Node.js or memory problem, TypeScript or lint errors, missing environment variables, plan limits, server code that is too large or uses Node.js APIs Workers do not have, timeouts and registry errors. Copy a prompt for your AI assistant puts the diagnosis and the relevant log lines (secrets removed) on your clipboard, ready to paste. Assistants and scripts can read the same thing with GET /api/v1/deployments/:id/explain.
When the failure is not one HostEdge recognises, the panel quotes the last error lines instead and says so. Start from the first error in the log, not the last.
Previews#
Deployments from branches other than the production branch are previews. They never touch production. Each branch has a moving URL that follows its latest preview, and pull requests get a comment with the link.
Redeploy, roll back, promote#
- Redeploy builds the same source again (useful after changing environment variables).
- Roll back points production at an earlier ready deployment instantly. No rebuild. You can undo it the same way.
- Promote makes a preview the production deployment.
Cancel#
Queued and building deployments can be canceled from the deployment page or the list.