wrangler-ops

name	wrangler-ops
description	Operational patterns for Cloudflare Wrangler CLI. Use when deploying workers, running D1 migrations, querying D1 databases, managing R2 buckets, or generating binding types. Distinct from cloudflare-api which covers documentation lookups.

wrangler-ops

Conventions and commands for working with the Cloudflare Wrangler CLI in projects.

Local Wrangler Config

Many projects have a gitignored local wrangler config (commonly wrangler.local.jsonc or wrangler.local.toml) that contains real account IDs, D1 database IDs, R2 bucket names, and worker names. The committed wrangler.jsonc has stub/placeholder values for distribution.

Always check for a local config first:

ls wrangler.local.* 2>/dev/null

If one exists, always pass it with -c:

pnpm exec wrangler deploy -c wrangler.local.jsonc
pnpm exec wrangler d1 migrations apply DB --remote -c wrangler.local.jsonc

Never modify or commit the local config. Never read .dev.vars -- it contains secrets.

Deploying

# Always use local config if it exists
pnpm exec wrangler deploy -c wrangler.local.jsonc

# Without local config
pnpm exec wrangler deploy

Deploy scripts are usually defined in package.json. Prefer those when available.

D1 Database Operations

Persistent State Directory

Dev servers often use --persist-to to store local D1 data in a shared directory (e.g. ). When querying local D1, you must pass the same flag so wrangler reads from the correct SQLite files.