cloudflare-r2-upload

You can upload local files to a Cloudflare R2 bucket using wrangler with OAuth or an API token, and generate public URLs by binding a custom public domain to the bucket. This process applies to both single-file and batched uploads, including post-upload URL verification.

To upload assets to an R2 bucket, you need to specify the BUCKET, KEY_PREFIX, and SRC_DIR configurations. You must also bind a PUBLIC_DOMAIN for URL construction, and provide a CLOUDFLARE_ACCOUNT_ID if you are handling multiple Cloudflare accounts.

Yes, Cloudflare R2 upload supports multi-account handling. When managing multiple Cloudflare accounts, you are required to explicitly provide your CLOUDFLARE_ACCOUNT_ID alongside the standard wrangler OAuth session or R2_API_KEY for successful asset publishing.

Yes, you can batch upload images and media from a local source directory to a specified Cloudflare R2 bucket. This workflow automatically generates stable public URLs for the uploaded assets by utilizing a bound custom domain.

A custom domain binding is needed to produce stable public URLs for your uploaded R2 files. By configuring the PUBLIC_DOMAIN for URL construction, the skill ensures your published site assets are publicly accessible and verifies the resulting URLs resolve correctly.

The best way to publish site assets to a public R2 bucket is using wrangler to batch upload local files and generate public URLs via a bound custom domain. This approach streamlines asset publishing by supporting OAuth sessions, API tokens, and post-upload URL verification.