No Dockerfile
The platform detects Nuxt from package.json, picks the build and start commands, and lists the environment variables your code reads.
Nuxt deploy guide · Agent Lab Deploy
Upload your Nuxt project as it is — no Dockerfile — or tell Claude Code, Codex or Cursor "deploy this". Agent Lab builds it into a web service, or a static web page when it is fully static, gives every version a preview URL with rollback, and checks uploads for leaked keys. Apps and databases run on Google Cloud in Taiwan.
> deploy this Nuxt app
sites_createmy-nuxt
sites_deployNuxt detected
sites_deploy_statusbuilt · secret scan passed
Live at my-nuxt--acme.hosting.agentlab.run
Why deploy Nuxt on Agent Lab
JavaScript / TypeScript project, built from source with no Dockerfile, deployed as a web service, or a static web page when it is fully static.
The platform detects Nuxt from package.json, picks the build and start commands, and lists the environment variables your code reads.
Every upload is a new version with its own URL. Look first, then go live; switch back to any version in one click.
Uploads are checked for API keys and credentials before they can go live. Secrets go in the console, never in the code.
Create a database and connect it; the connection is written into the app's environment and the password is never shown.
Your options
Scroll the table sideways.
| What you care about | Agent Lab Deploy | Your own VPS |
|---|---|---|
| Setup | Upload or say one sentence; no Dockerfile | SSH, a runtime, a process manager, a reverse proxy |
| HTTPS and domains | Automatic, custom domains on paid plans | Certbot and DNS by hand |
| Preview and rollback | Every version has its own URL; roll back in one click | Write your own scripts |
| Before going live | Uploads checked for leaked keys | Nothing unless you set it up |
| Database | PostgreSQL in one click, connection written into the app | Install and back it up yourself |
| Cost to start | Free plan: NT$0, one size-S app (sleeps when idle) | A VPS at roughly NT$200–600 a month, plus your time |
Steps
Keep package.json at the top of the project and commit the lockfile. Leave out node_modules, .git, dist and .env.
Drop the folder on a project's Deploy tab, push from GitHub, or ask your AI tool through Agent Lab MCP.
The platform builds the version and checks it for leaked keys. Enter any secrets it lists in Settings.
The first version goes live once it builds. Later ones get a preview URL; go live when you're happy.
Setup
The platform reads runtimeConfig in nuxt.config and lists the variables the code needs, marking secrets and build-time ones, before you deploy. NUXT_PUBLIC_ values are sent to the browser; never put a secret there.
# Agent Lab 偵測到 Nuxt 後執行
# What Agent Lab runs once it detects Nuxt
npm ci
npm run build # nuxt build(Nitro node-server)
node .output/server/index.mjs # 監聽 $PORT(預設 8080)
# nuxt generate 的純靜態網站 → 改成靜態網頁,放 CDNPORT the port the platform gives (8080 by default); the server must listen on it.NUXT_* runtimeConfig keys map automatically, e.g. runtimeConfig.apiSecret → NUXT_API_SECRET.NUXT_SESSION_PASSWORD with nuxt-auth-utils, generate it in the console (at least 32 characters).DATABASE_URL written for you when you connect an Agent Lab PostgreSQL.Read https://app.agentlab.cresclab.com/agent/deploy.md and deploy this Nuxt project to Agent Lab. Show me the build plan and the environment variables it needs first, tell me where to enter any secrets, and wait for my OK before it goes live.FAQ