Deploy with Docker, Git, or ZIP on Nivi Cloud

Use Source & Build when you are not launching from a one-click Template, or when you want to replace the current app’s source. Open Manage → Source & Build (also linked as Source & Deployment from Overview).

Deploy modes

Source & Build → Docker Image

Source & Build → Dockerfile

Source & Build → Upload Archive

Build strategies

Depending on your source, Nivi Cloud can build with:

• Nixpacks — auto-detect common languages/frameworks
• Dockerfile — use your Dockerfile
• Buildpacks — Cloud Native Buildpacks-style builds
• Railpack — alternate pack-based builds

If you only supply a repository or ZIP without a Dockerfile, automatic detection (for example Nixpacks) is usually enough.

Recommended flow

1. Choose a deploy mode and fill the required fields carefully (branch names and build paths matter).
2. Set any required Environment variables before or right after the first deploy (KEY=VALUE, one per line; # comments allowed).
3. Deploy / Save as shown in the UI.
4. Watch Live Logs until the app is healthy, then open the testing URL.
5. Attach a custom domain when DNS is ready.

Environment → KEY=VALUE (secrets redacted in this example)

Important notes

• On plans with a 1 app limit, deploying a new custom source typically replaces the current application. Confirm you are ready to replace an existing stack before continuing.
• Some Source screens include a Deploy Service control that can trigger a redeploy of the current configuration — review the active mode before clicking.
• Private Docker registries need valid credentials in the Docker Image form.
• Private GitHub repos require connecting/authenticating as offered in the GitHub mode.