One deployment per branch
A Zonda Cloud app can have several branches linked at once: each one has its own running deployment and its own address, without affecting the main branch.
Link a branch
On the app page, the Branches card lists the branches of your repository that are not linked yet. When you link one, it is deployed right away and deployed again on every push to that branch. A push to a branch you did not link deploys nothing: there are no automatic deployments of branches you did not choose.
The address of each branch
The main branch keeps the app’s address, mi-app.zondacloud.com. The others are served at mi-app--staging.zondacloud.com: the app name, two hyphens and the branch name, normalized to lowercase letters, numbers and hyphens (feature/Login becomes feature-login).
What each branch has
- Its own running deployment, which is replaced automatically when you push to that branch.
- Its own history, logs, redeploy and rollback.
- Optionally, custom domains: each domain points to one branch.
Environment variables and build settings belong to the app and are shared across branches.
Unlinking and limits
When you unlink a branch, its deployment is stopped and it is no longer served, but its history and its domains are kept: if you link it again, they work again. The main branch cannot be unlinked. Because each branch is an active deployment that uses resources, each account has a limit on the number of branches per app.