Deployment

Run deploy from the app directory.

nstack deploy

The deploy flow discovers Encore resources, renders deploy files, provisions the Dokploy target, rebuilds generated client code, deploys backend and frontend services, and verifies the published URL.

Targets

Targets represent Dokploy environments such as production or staging.

nstack target create staging --domain staging.example.com

Use targets when the same app needs separate domains, secrets, resource instances, or deployment history.

Generated deploy output

During deploy, nstack renders the resource plan and Dokploy service definitions from source. Treat those files as CLI output and change the app code or target config when the deploy shape needs to change.

Generated Compose keeps infrastructure credentials as environment references. After declaring a new database, cache, or object storage bucket, run nstack deploy once before relying on automatic push deployment.

When an initial push creates a Gitea or Forgejo repository, nstack explicitly requests private visibility.

Experimental rolling deploys

Dokploy's regular Compose deployment is the default. To test nstack's health-gated rollout, set deploy.zeroDowntime to true in nstack.config.mjs, then run nstack deploy.

The experimental rollout starts replacement backend and frontend containers and waits for their health checks before removing the current containers. Keep database migrations compatible with both backend versions during the handoff. Run nstack deploy again after disabling the option so automatic provider-backed pushes return to Dokploy's regular Compose command.

After deploy

Check status and follow logs from the same CLI.

nstack status
nstack logs --follow