Deploy from a Git repository
Connect a public repository, choose the right build pack, and configure auto deploy, build commands and preview deployments.
Git repo is the default source for a cloud hosting app. It works with GitHub, GitLab, Bitbucket or any HTTPS Git URL that is publicly readable.
Create the app
- Console → Websites & Apps → New deployment.
- Choose Git repo.
- Fill in:
- Git repository URL —
https://github.com/you/project.git - Branch —
main,production, or whatever you deploy from - Build pack — see below
- Git repository URL —
- Continue to Destination, give the app a name and optionally a domain.
- Pick a Plan slot and choose Deploy — uses 1 slot.
For a private repository, use the GitHub source instead. Private HTTPS URLs with a token pasted into the URL are not supported.
Choosing a build pack
| Build pack | Use it when |
|---|---|
| Nixpacks (Auto-detect) | Default. Detects Node, Python, Go, Ruby, PHP, Rust, Java and more |
| Railpack | The repository already works with Railpack, or you want its build behaviour |
| Static Site | The build produces static files (HTML/CSS/JS) and needs no server process |
| Dockerfile | The repository contains a Dockerfile |
| Docker Compose | The repository contains a compose file that describes the service |
Nixpacks is right for most projects. If the auto-detected build fails, the log usually shows which package manager or runtime it guessed; you can override the install, build and start commands under Settings → Build.
Build settings
Settings → Build exposes:
- Install command, Build command, Start command
- Base directory — for monorepos, the subdirectory to build
- Publish directory — where static output lands
- Static site and Single-page app toggles
Leave a field blank to use the build pack's detection.
Auto deploy on push
Under Settings → Source:
- Auto deploy on push — rebuild and deploy on every push to the selected branch.
- Preview deployments for pull requests — build pull requests and give each one a URL.
- Git submodules, Git LFS, Shallow clone — enable if the repository needs them.
With auto deploy on, the deployment appears in Deployments seconds after the push. With it off, use Redeploy on the app or deployment page.
Webhooks
Pushes are detected through the Git provider's webhook, which is configured when you add the repository. If pushes stop triggering builds:
- Confirm Auto deploy on push is still enabled.
- Check that the branch in the app settings matches the branch you push to.
- Use Redeploy once to confirm the build itself works.
- If only webhooks fail, reconnect the source or contact support with the repository URL and the time of the push.
Changing the branch
Update Settings → Source → Branch and save. The next deployment builds from the new branch. The currently running release stays live until the new build succeeds.
Monorepos
Set Base directory to the folder containing the app. If several apps come from one repository, create one Zoophost app per folder and give each its own base directory and domain.
What gets built
Only the repository content at the selected commit is available to the build. Large files that are not committed — .env files, local databases, uploaded assets — are not present. Supply configuration through environment variables and keep uploaded files in Z2 Object Storage.
Next
- git
- repository
- branch
- build pack
- nixpacks
- auto deploy
Ready to use this
Git-push containers, previews and custom domains, billed monthly in INR.
- 5 websites on the smallest plan
- Free SSL and custom domains

