/deno-deploy

Framework-Specific Deployment

Deno Deploy supports multiple frameworks. The CLI auto-detects your framework and configures the build appropriately.

Framework Detection

Framework Presets for deno deploy create

When creating an app with deno deploy create in non-interactive mode, you can specify --framework-preset to auto-configure build commands and runtime settings. The available presets are: Fresh, Next, Remix, Astro, SvelteKit, Nuxt, Lume, SolidStart.

When a preset is specified, you can omit --install-command, --build-command, --pre-deploy-command, and --runtime-mode — they are inferred from the preset.

If you don't specify a preset, the CLI still auto-detects your framework from the project files. Use --do-not-use-detected-build-config to skip auto-detection and specify everything manually.

Detect Framework Script

if [ -d "islands" ] || [ -f "fresh.config.ts" ]; then echo "Framework: Fresh"; \
elif [ -f "astro.config.mjs" ] || [ -f "astro.config.ts" ]; then echo "Framework: Astro"; \
elif [ -f "next.config.js" ] || [ -f "next.config.mjs" ]; then echo "Framework: Next.js"; \
elif [ -f "nuxt.config.ts" ]; then echo "Framework: Nuxt"; \
elif [ -f "remix.config.js" ]; then echo "Framework: Remix"; \
elif [ -f "svelte.config.js" ]; then echo "Framework: SvelteKit"; \
elif [ -f "_config.ts" ]; then echo "Framework: Lume (check imports)"; \
else echo "Framework: Custom/Unknown"; fi

Fresh (Deno-Native)

deno task build
deno deploy --prod

Fresh + PostgreSQL

When a Fresh app uses PostgreSQL (e.g., await initDb() at startup), you must provision the database before the app can successfully warm up. The Fresh auto-detection preset also has a known issue, so use manual build config.

Complete deployment sequence:

# 1. Create the app with --no-wait (warmup will fail without a database — that's expected)
deno deploy create \
  --org <ORG_NAME> --app <APP_NAME> \
  --source local \
  --do-not-use-detected-build-config \
  --install-command "deno install" \
  --build-command "deno task build" \
  --pre-deploy-command "echo ready" \
  --runtime-mode dynamic --entrypoint main.ts \
  --build-timeout 5 --build-memory-limit 1024 --region us \
  --no-wait

# 2. Provision a PostgreSQL database
deno deploy database provision my-db --kind prisma --region us-east-1

# 3. Assign it to the app (this injects DATABASE_URL, PGHOST, etc.)
deno deploy database assign my-db --app <APP_NAME>

# 4. Redeploy — now the database exists, so warmup succeeds
deno deploy --prod

Why this order matters:

• Fresh + PostgreSQL apps typically call await initDb() in main.ts, which runs during warmup
• If no database is assigned, the connection fails and the deploy is marked as failed
• Using --no-wait on the first deploy lets you continue to the database setup without blocking

Why --do-not-use-detected-build-config:

• The Fresh auto-detection and --framework-preset fresh can fail with an API error
• Manual build config is more reliable — see Troubleshooting

Astro

# If using npm
npm run build
deno deploy --prod

# If using Deno tasks
deno task build
deno deploy --prod

Next.js

Next.js requires Node.js compatibility mode:

1. Ensure deno.json has:

   {
     "nodeModulesDir": "auto"
   }

2. Build and deploy:

   npm install
   npm run build
   deno deploy --prod --allow-node-modules

Nuxt / Remix / SvelteKit / SolidStart

These npm-based frameworks follow a similar pattern:

npm install
npm run build
deno deploy --prod

If you encounter issues with node_modules:

deno deploy --prod --allow-node-modules

Lume (Static Sites)

deno task build
deno deploy --prod

Custom / No Framework

For custom servers or apps without a recognized framework:

1. Ensure you have an entrypoint (e.g., main.ts, server.ts)
2. Deploy directly:

   deno deploy --entrypoint main.ts --prod

Static Site Deployment

For static sites (Lume, Vite builds, etc.), you have two options:

Option 1: Direct Directory Deployment

Point Deno Deploy at your built directory. Configure in deno.json:

{
  "deploy": {
    "entrypoint": "main.ts",
    "include": ["_site"]
  }
}

Option 2: Custom Server Wrapper

Only needed if you want custom routing, headers, or logic:

// serve.ts
import { serveDir } from "jsr:@std/http/file-server";

Deno.serve((req) =>
  serveDir(req, {
    fsRoot: "_site",
    quiet: true,
  })
);

Then deploy with:

deno deploy --entrypoint serve.ts --prod

Cloud Integrations

AWS Integration

deno deploy setup-aws --org my-org --app my-app

GCP Integration

deno deploy setup-gcp --org my-org --app my-app