Production Ship & operate

Explicit production deploys with inspectable output

Production uses or , preview uses or . No target means no deploy.

Devflare resolves config, generates Wrangler artifacts, and deploys against an explicit destination.

Best for: Production deploys and preflight checks
Required target: , , , or
Best debug habit: Inspect compiled output before deploying

The production lane

Refresh generated types when bindings or entrypoints changed, build once, inspect when the setup changed, then deploy with an explicit production target.

The CLI page owns the broad command map. This page covers how those commands fit the release lane.

1

Run when bindings or entrypoints changed and needs to catch up.
2

Run to generate production artifacts.
3

Use or when the compiled result needs inspection before release.
4

Run or only when the target is unmistakably production. Add first if you want to verify the pipeline without pushing.

Need the full command map?

Open the CLI page when the question is what , , , or generally do. This page only covers how those commands fit the production release lane.

Production release workflow with an explicit target

Keep the same local release lane visible in CI: generate types, build production output, dry-run the deploy, then push only with `--prod`.

name: Production

on:

push:

branches: [main]

jobs:

deploy:

runs-on: ubuntu-latest

permissions:

contents: read

deployments: write

steps:

- uses: actions/checkout@v4

- uses: oven-sh/setup-bun@v2

- run: bun install --frozen-lockfile

- run: bunx --bun devflare types

- run: bunx --bun devflare build --env production

- run: bunx --bun devflare deploy --prod --dry-run

- run: bunx --bun devflare deploy --prod

Production deploys are explicit

Deploy requires an explicit target so production and preview stay unmistakable. Production is or ; preview is or .

Production deploys also clear preview-scope overrides like so stable worker names point at stable infrastructure.

No target means no deploy

Intentional. Keeps production vs. preview intent visible in CI logs and command history.

Stricter verification in automation

The reusable deploy action exposes and so CI can fail when Cloudflare cannot confirm the expected version.

Production deploy commands

bunx --bun devflare build --env production

bunx --bun devflare deploy --prod

bunx --bun devflare deploy --production --message "Release 1" --tag release-1

Preflight tools

— run the full deploy pipeline without pushing anything to Cloudflare.
— see the compiled deployment shape.
— check config resolution, Vite opt-in, and generated files.
before deploy — when the package just gained new bindings, routes, or framework wiring.

Deploy recipes

Use build, dry-run, production deploy, named preview deploy, same-worker preview upload, cleanup, and GitHub Actions as separate recipes with visible effects.

Monorepos & Turborepo

Turbo owns task orchestration and caching. still runs from the package that owns the Worker or app.