Preview environments
Preview environments give each branch its own deployment with its own URL — so you can see a change running before it reaches production. Previews are tied to your git connection: connect a repo, and Cantila can build previews per branch.
How it works
When git is connected, Cantila creates a preview deployment for a branch,
each with a distinct URL you can share for review. Scope variables to
previews with the preview scope — see env & secrets.
curl https://api.cantila.app/v1/projects/PROJECT_ID/previews \
-H "Authorization: Bearer <api_key>"Requirements
| Need | Why |
|---|---|
| A git connection | Previews are driven per branch from your repo |
| Branch + auto-deploy honored | Cantila builds the branch on changes |
Preview automation is maturing.
Per-branch preview deployments and their URLs are in place. Some of the surrounding automation is still maturing — check the git page and the changelog for the current state before relying on a specific behavior.
Related
- Push-to-deploy (git)
- Env & secrets — the
previewscope - Logs & metrics