Nuxt template

The DockIY Nuxt template provides a flexible Nuxt application foundation with encrypted configuration and separate staging and production deployments. It does not prescribe a database or authentication system.

Try the deployed demo.

For an opinionated full-stack starter, use the Nuxt Better Auth template.

Stack

• Nuxt 4, Vue, TypeScript, and Nitro
• Tailwind CSS, shadcn-vue, and Reka UI
• VueUse
• ESLint, eslint-plugin-tailwindcss, Husky, and lint-staged
• Docker Compose and Traefik
• SOPS with age

The application image contains Nuxt's built .output. It does not contain build tools, source files, or secrets.

Requirements

Install these tools on your computer:

• Node.js 24+
• pnpm 11+
• Git
• Docker Engine and Docker Compose
• SOPS and an SOPS identity for encrypted deployment values
• the DockIY CLI for deployment

Develop locally

Create a project with dockiy app init nuxt my-app, or clone the template. Then run:

pnpm install --frozen-lockfile
pnpm dev

Nuxt runs at localhost:3000. The checked-in runtime defaults need no environment file. Copy .env.example to .env when you want to override them.

Verify changes before committing:

pnpm lint
pnpm typecheck
pnpm build

Configure deployment

The DockIY base stack must already be running. In dockiy.yml at the project root, edit name and the host values under environments.staging and environments.production:

name: my-app

environments:
  staging:
    host: staging.example.com
    compose_file: docker-compose.yml
    secrets_file: .enc.staging.env
  production:
    host: example.com
    compose_file: docker-compose.yml
    secrets_file: .enc.production.env

Set the VPS connection in the global DockIY config. For a checkout-specific override, create an uncommitted dockiy.config.yml in the project root. See the configuration reference for the config file locations and precedence.

Edit encrypted deployment values in the project root with SOPS:

sops edit .enc.staging.env
sops edit .enc.production.env

When using dockiy app init, follow the prompt to create a fresh SOPS config. When cloning directly, replace the template's .sops.yaml and encrypted files with your own recipients and values. Add application secrets to the encrypted files and map them into the app service in docker-compose.yml.

Deploy

Commit the application, then follow Deploying applications for the deployment, status, version, and rollback commands:

git add .
git commit -m "feat: configure application"
dockiy app deploy staging
dockiy app deploy production --version v1.0.0