Publishing is a separate action from building. A build that passed is a zip on the server; publishing is what turns it into a page someone else can open. The split is deliberate: passing a gate should not be the same click as going public.
What publish requires
Two things: the build state is done, and an artifact exists. If you press publish on a build that passed but has no zip, the server answers artifact-required rather than publishing an empty page. That error means the export step did not run, not that the build failed.
What you get
- An address on the Myrax host, derived from the project name and made unique, served over HTTPS.
- Your own domain, if you set one. See Custom domains.
- A record of when it was published, so an old build is distinguishable from a new one.
What is inside the zip
The workspace, minus the things that must never ship:
| Included | Excluded |
|---|---|
| HTML, CSS, JS, assets, and other project files | .env and .env.* |
A MYRAX-EXPORT.json manifest with the file count | *.pem, *.key |
| The sha256 of the archive, recorded with the build | node_modules, .git |
The exclusion list is enforced during packing, not by convention, and every file that is skipped is recorded so you can see what was left out.
Taking a site down
Taking down asks you to type the build name first, because it is the one action here that a visitor will notice immediately. The build itself is not deleted: the artifact and snapshots stay, so the site can go back up.
Republishing
A published build keeps its address. Publishing again after a new passing build replaces what is served at that address; the old artifact stays on disk until it is cleaned up. That is why an address is stable and a build is not.
Shares
A share link is separate from publishing and narrower: it exposes one build read-only to someone without an account. Revoking a share asks for confirmation and takes effect immediately. If you want something public and permanent, that is publishing; if you want to show one person a draft, that is a share.
Where a published build sits in the whole flow: How a build works.

