nstack-demo5

Encore + Nuxt app deployed by nstack.

Local

pnpm install
pnpm dev

Deploy

Point the domain at your Dokploy server. If this app was not linked during nstack init, run:

nstack configure --domain <domain> --dokploy-url https://dokploy.example.com --dokploy-api-key <key> --repository https://github.com/acme/nstack-demo5.git
nstack deploy

After that, the usual loop is small:

pnpm check
nstack deploy
nstack status

Deploy settings live in .nstack/local.env. App runtime secrets live in .nstack/secrets.env.

For deploy-on-push, connect the matching Git provider in Dokploy first. nstack can configure provider-backed Compose sources for GitHub, GitLab, Bitbucket, and Gitea/Forgejo. Use deploy.source in nstack.config.mjs for advanced provider fields such as explicit provider ids, GitLab path namespace, Bitbucket slug, or custom plain-Git SSH key id.

Secrets

nstack env set API_SECRET
nstack env push

Use nstack env pull --all when remote env changed and you want to refresh local secrets.

Recovery

nstack doctor
nstack logs --follow
nstack pull
nstack rollback

nstack provisions declared Encore resources automatically. Dokploy Domains/Traefik handle ingress; there is no proxy container in this template. By default Dokploy builds the production Nuxt server and Encore backend from source through Compose, so no external image registry is required.

Encore cron jobs are registered as Dokploy schedules. Keep cron endpoints private with api({ expose: false }, ...); Dokploy executes them through the bundled backend cron runner instead of calling a public HTTP route.