From commit to live
1
Commit
A
commit validates the workspace config and workflow declarations, pushes to the workspace repo, and
builds a snapshot in the background. Each
commit is a version.2
Publish
publish_app pins the latest successful build as the published version. If the build is still
running or failed, publishing is blocked until it’s green.3
Serve
The app deploys to an edge worker at
https://<subdomain>.zite.so (or your custom domain). External
apps are public; internal apps require signing in with Zite.publish_app) or from the editor.
Internal vs external
Internal apps
Open only to the organization members you give access to, who sign in with Zite. Served at
https://<subdomain>.zite.so (or your custom domain).External apps
Deployed to a public edge worker at
https://<subdomain>.zite.so (or your custom domain), with the
app’s sign-in for its users.Versions & rollback
Every version is backed by a commit and its snapshot. From the version history (the history icon in the header of the editor’s chat panel) you can:- Browse previous versions and preview them.
- Restore an earlier version to roll back. Restoring creates a new version with that version’s contents, so the later versions stay in the history.
Custom domains
By default an app is served at its app ID onzite.so. Once an app is published, its Settings →
Link tab lets you set:
- A custom Zite subdomain, such as
yourname.zite.so. - A custom domain you own, on the Pro plan (one domain) or Business and above. Point a subdomain at Zite
with a CNAME record, or a root domain with A records (plus a CNAME for
www); the tab shows the exact records. TLS is handled automatically.