Overview
Configure your Conductor deployment usingwrangler.toml, the configuration file for Cloudflare Workers. This guide covers all configuration options for running Conductor workflows at the edge.
Basic Configuration
Minimal Setup
Complete Setup
Configuration Sections
Worker Settings
AI Binding
Database (D1)
KV Storage
R2 Storage
Vectorize
Durable Objects
Queues
Environment Configuration
Multiple Environments
Environment Variables
vars for non-sensitive configuration. For secrets (API keys, tokens), use Secrets Management.
Resource Limits
Worker Limits
D1 Limits
- Max database size: 10GB (can request increase)
- Max rows per table: No limit
- Max query execution time: 30 seconds
- Max queries per request: 50
KV Limits
- Max key size: 512 bytes
- Max value size: 25MB
- Max metadata size: 1KB
- Read operations: 100,000 per day (free), unlimited (paid)
- Write operations: 1,000 per day (free), unlimited (paid)
R2 Limits
- Max object size: 5TB
- Max multipart upload: 10,000 parts
- Storage: 10GB free, then pay-as-you-go
Vectorize Limits
- Max dimensions: 1536
- Max vectors per index: 5 million (can request increase)
- Max queries per second: 1,000
Custom Routes
Route Patterns
Custom Domains
Build Configuration
TypeScript
ESBuild Options
Observability
Logpush
Tail Workers
Cron Triggers
Best Practices
- Use compatibility dates - Keep up to date with latest features
- Separate environments - dev, staging, production
- Don’t commit secrets - Use
wrangler secretfor sensitive data - Test locally first - Use
wrangler devbefore deploying - Monitor limits - Track resource usage in dashboard
- Version migrations - Increment migration tags for DO changes
- Use preview bindings - Separate dev/production data
- Document configuration - Add comments explaining settings
- Backup data - Regular backups of D1 databases
- Review costs - Monitor usage and optimize

