Skip to content
amn Docs

outputs cmd

  1. wrangler r2 bucket create medias-r2-dev

⛅️ wrangler 4.129.0 ──────────────────── Creating bucket ‘medias-r2-dev’… ✅ Created bucket ‘medias-r2-dev’ with default storage class of Standard. To access your new R2 Bucket in your Worker, add the following snippet to your configuration file: { “r2_buckets”: [ { “bucket_name”: “medias-r2-dev”, “binding”: “medias_r2_dev” } ] }

  1. wrangler r2 bucket create backups-r2-dev

⛅️ wrangler 4.129.0 ──────────────────── Creating bucket ‘backups-r2-dev’… ✅ Created bucket ‘backups-r2-dev’ with default storage class of Standard. To access your new R2 Bucket in your Worker, add the following snippet to your configuration file: { “r2_buckets”: [ { “bucket_name”: “backups-r2-dev”, “binding”: “backups_r2_dev” } ] }

  1. wrangler r2 bucket create backups-r2-prod

⛅️ wrangler 4.129.0 ──────────────────── Creating bucket ‘backups-r2-prod’… ✅ Created bucket ‘backups-r2-prod’ with default storage class of Standard. To access your new R2 Bucket in your Worker, add the following snippet to your configuration file: { “r2_buckets”: [ { “bucket_name”: “backups-r2-prod”, “binding”: “backups_r2_prod” } ] }

  1. wrangler r2 bucket create medias-r2-prod

⛅️ wrangler 4.129.0 ──────────────────── Creating bucket ‘medias-r2-prod’… ✅ Created bucket ‘medias-r2-prod’ with default storage class of Standard. To access your new R2 Bucket in your Worker, add the following snippet to your configuration file: { “r2_buckets”: [ { “bucket_name”: “medias-r2-prod”, “binding”: “medias_r2_prod” } ] }

  1. wrangler queues create submissions-queue-prod

⛅️ wrangler 4.129.0 ──────────────────── 🌀 Creating queue ‘submissions-queue-prod’ ✅ Created queue ‘submissions-queue-prod’

Configure your Worker to send messages to this queue:

{ “queues”: { “producers”: [ { “queue”: “submissions-queue-prod”, “binding”: “submissions_queue_prod” } ] } } Configure your Worker to consume messages from this queue:

{ “queues”: { “consumers”: [ { “queue”: “submissions-queue-prod” } ] } }

  1. wrangler queues create submissions-queue-dev

⛅️ wrangler 4.129.0 ──────────────────── 🌀 Creating queue ‘submissions-queue-dev’ ✅ Created queue ‘submissions-queue-dev’

Configure your Worker to send messages to this queue:

{ “queues”: { “producers”: [ { “queue”: “submissions-queue-dev”, “binding”: “submissions_queue_dev” } ] } } Configure your Worker to consume messages from this queue:

{ “queues”: { “consumers”: [ { “queue”: “submissions-queue-dev” } ] } }

  1. wrangler kv namespace create WEBHOOK_LOCK_PROD

⛅️ wrangler 4.129.0 ──────────────────── Resource location: remote

🌀 Creating namespace with title “WEBHOOK_LOCK_PROD” ✨ Success! To access your new KV Namespace in your Worker, add the following snippet to your configuration file: { “kv_namespaces”: [ { “binding”: “WEBHOOK_LOCK_PROD”, “id”: “f1f107098b5e493bbf95fa495902c94f” } ] }

  1. wrangler kv namespace create WEBHOOK_LOCK_DEV

⛅️ wrangler 4.129.0 ──────────────────── Resource location: remote

🌀 Creating namespace with title “WEBHOOK_LOCK_DEV” ✨ Success! To access your new KV Namespace in your Worker, add the following snippet to your configuration file: { “kv_namespaces”: [ { “binding”: “WEBHOOK_LOCK_DEV”, “id”: “2adb511a55424659a383d95d2c302102” } ] }