cloudflare-worker-deployment

Deploy Hono TypeScript apps to Cloudflare Workers by configuring wrangler.toml with your entrypoint (app.ts or index.ts), setting compatibility_date, and running wrangler deploy. This Skill automates wrangler.toml setup, multi-environment configuration, and binding declarations to streamline the entire deployment process.

Bindings connect your Worker to Cloudflare services. Configure D1 databases, R2 storage, KV namespaces, and Durable Objects in wrangler.toml under the [env] sections for each environment. This Skill handles binding declarations and environment-specific overrides to ensure correct wiring across dev, staging, and production.

Manage secrets using wrangler secret commands and environment variables via the [vars] section in wrangler.toml. This Skill automates secure secret management configuration and environment-specific variable setup so sensitive data is handled correctly across all deployment stages.

Yes. Cloudflare Workers supports multi-environment deployments through environment-specific sections in wrangler.toml. This Skill configures dev, staging, and production environments with separate bindings, variables, and compatibility settings in a single repeatable configuration file.

Use a base configuration with [env.development], [env.staging], and [env.production] sections, each specifying route patterns, bindings, and variables. This Skill generates the complete wrangler.toml structure with proper compatibility_date, build configuration, and environment-specific overrides.

Wrangler handles most build configuration automatically, but you must specify the correct entrypoint (app.ts or index.ts) in wrangler.toml. This Skill defines build and entrypoint configuration and ensures proper Wrangler-based deployment workflows for Hono backends.