Publishing a site creates an HTTP user service under the hood. The site runs a production build and gets a dedicated, memorable URL that works from anywhere — not just the preview iframe.Documentation Index
Fetch the complete documentation index at: https://docs.zocomputer.com/llms.txt
Use this file to discover all available pages before exploring further.
What publishing does
- Runs the site as a production service (not the dev server)
- Assigns a dedicated URL you can share and access from any browser
- Public sites (default): URL at *.zocomputer.io, accessible to anyone without sign-in
- Private sites: URL at *.zo.computer, requires the owner to be signed in
Before publishing
The site is already running (dev server) and accessible to the signed-in user at its authenticated preview URL (zite--.zo.computer) and via the preview iframe in the Zo web app. Publishing upgrades it to a production build with a clean URL. Do NOT use register_user_service or update_user_service for sites — use this tool instead. The publish config (label, port, entrypoint) is read from the site’s zosite.json.Parameters
Required. Workspace-relative directory that contains the site’s zosite.json (e.g. ‘my-site’ or ‘projects/my-site’).
Whether the published site is publicly accessible. ‘true’ (default): URL at *.zocomputer.io, no sign-in required. ‘false’: URL at *.zo.computer, requires owner sign-in.