The publish flow
What happens when you click Publish, end-to-end.
Step by step #
- Snapshot Your workspace is git-tagged at this moment as a release.
- Build A Docker image is built from the snapshot. Cached layers make this fast — typically under 30s after the first build.
- Push The image is pushed to the registry.
- Run A container starts on a runtime host with your real credentials injected as env vars.
- Health check Vibe waits for the container to respond on /health before routing traffic.
- Route Caddy's host map is updated. Your subdomain (and any custom domain) now point at the new container.
Deploy messages #
The publish dialog has a free-form message field. These messages show up in the Deploys tab and are useful when you need to track down which release caused a regression.
Where publishing sits in the bigger picture #
Publishing moves one layer of your app — the interface — onto a host and gives it an address. It never touches the layer below: your tables, workflows and security rules are already live, and a publish neither migrates nor re-secures them.