Wrangler
by @asleep123
Manage Cloudflare Workers, KV, D1, R2, and secrets using the Wrangler CLI. Use when deploying workers, managing databases, storing objects, or configuring Cloudflare resources. Covers worker deployment, KV namespaces, D1 SQL databases, R2 object storage, secrets management, and tailing logs.
clawhub install wranglerπ About This Skill
name: cloudflare description: Manage Cloudflare Workers, KV, D1, R2, and secrets using the Wrangler CLI. Use when deploying workers, managing databases, storing objects, or configuring Cloudflare resources. Covers worker deployment, KV namespaces, D1 SQL databases, R2 object storage, secrets management, and tailing logs.
Cloudflare (Wrangler CLI)
Manage Cloudflare Workers and associated services via the wrangler CLI.
Prerequisites
npm install -g wrangler or use project-local npx wranglerwrangler login (opens browser for OAuth)wrangler whoamiQuick Reference
Workers
# Initialize new worker
wrangler init Local development
wrangler dev [script]Deploy
wrangler deploy [script]List deployments
wrangler deployments listView deployment
wrangler deployments view [deployment-id]Rollback
wrangler rollback [version-id]Delete worker
wrangler delete [name]Tail logs (live)
wrangler tail [worker]
Secrets
# Add/update secret (interactive)
wrangler secret put Add secret from stdin
echo "value" | wrangler secret put List secrets
wrangler secret listDelete secret
wrangler secret delete Bulk upload from JSON file
wrangler secret bulk secrets.json
KV (Key-Value Store)
# Create namespace
wrangler kv namespace create List namespaces
wrangler kv namespace listDelete namespace
wrangler kv namespace delete --namespace-id Put key
wrangler kv key put --namespace-id Get key
wrangler kv key get --namespace-id Delete key
wrangler kv key delete --namespace-id List keys
wrangler kv key list --namespace-id Bulk operations (JSON file)
wrangler kv bulk put --namespace-id
wrangler kv bulk delete --namespace-id
D1 (SQL Database)
# Create database
wrangler d1 create List databases
wrangler d1 listDatabase info
wrangler d1 info Execute SQL
wrangler d1 execute --command "SELECT * FROM users"Execute SQL file
wrangler d1 execute --file schema.sqlLocal execution (for dev)
wrangler d1 execute --local --command "..."Export database
wrangler d1 export --output backup.sqlDelete database
wrangler d1 delete Migrations
wrangler d1 migrations create
wrangler d1 migrations apply
wrangler d1 migrations list
R2 (Object Storage)
# Create bucket
wrangler r2 bucket create List buckets
wrangler r2 bucket listDelete bucket
wrangler r2 bucket delete Upload object
wrangler r2 object put / --file Download object
wrangler r2 object get / --file Delete object
wrangler r2 object delete /
Queues
# Create queue
wrangler queues create List queues
wrangler queues listDelete queue
wrangler queues delete
Configuration Files
Wrangler supports both TOML and JSON/JSONC config formats:
wrangler.toml β traditional formatwrangler.json or wrangler.jsonc β newer, with JSON schema supportβ οΈ Important: If both exist, JSON takes precedence. Pick one format to avoid confusion where edits to TOML are ignored.
JSONC format (with schema autocomplete)
{
"$schema": "./node_modules/wrangler/config-schema.json",
"name": "my-worker",
"main": "src/index.ts",
"compatibility_date": "2024-12-30"
}
TOML format
name = "my-worker"
main = "src/index.ts"
compatibility_date = "2024-12-30"
With bindings:
name = "my-worker"
main = "src/index.ts"
compatibility_date = "2024-12-30"KV binding
[[kv_namespaces]]
binding = "MY_KV"
id = "xxx"D1 binding
[[d1_databases]]
binding = "DB"
database_name = "my-db"
database_id = "xxx"R2 binding
[[r2_buckets]]
binding = "BUCKET"
bucket_name = "my-bucket"Environment variables
[vars]
API_URL = "https://api.example.com"Secrets (set via wrangler secret put)
Referenced as env.SECRET_NAME in worker code
Static assets (for frameworks like Next.js):
name = "my-site"
main = ".open-next/worker.js"
compatibility_date = "2024-12-30"
compatibility_flags = ["nodejs_compat"][assets]
directory = ".open-next/assets"
binding = "ASSETS"
Common Patterns
Deploy with environment
wrangler deploy -e production
wrangler deploy -e staging
Custom domain (via dashboard or API)
Custom domains must be configured in the Cloudflare dashboard under Worker Settings > Domains & Routes, or via the Cloudflare API. Wrangler doesn't directly manage custom domains.
Local development with bindings
# Creates local D1/KV/R2 for dev
wrangler dev --local
Checking deployment status
wrangler deployments list
wrangler deployments view
What Wrangler Does NOT Do
For DNS/domain management, see the cloudflare skill (uses Cloudflare API directly).
Troubleshooting
| Issue | Solution |
|-------|----------|
| "Not authenticated" | Run wrangler login |
| Node version error | Requires Node.js v20+ |
| "No config found" | Ensure config file exists (wrangler.toml or wrangler.jsonc) or use -c path/to/config |
| Config changes ignored | Check for wrangler.json/wrangler.jsonc β JSON takes precedence over TOML |
| Binding not found | Check wrangler.toml bindings match code references |
Resources
βοΈ Configuration
npm install -g wrangler or use project-local npx wranglerwrangler login (opens browser for OAuth)wrangler whoamiπ Tips & Best Practices
| Issue | Solution |
|-------|----------|
| "Not authenticated" | Run wrangler login |
| Node version error | Requires Node.js v20+ |
| "No config found" | Ensure config file exists (wrangler.toml or wrangler.jsonc) or use -c path/to/config |
| Config changes ignored | Check for wrangler.json/wrangler.jsonc β JSON takes precedence over TOML |
| Binding not found | Check wrangler.toml bindings match code references |