Deploy Blazor WebAssembly to Bunny Storage

A standalone Blazor WebAssembly app publishes as static files that run in the browser. Publishing to bin/publish puts the site in bin/publish/wwwroot, a path that doesn’t change with your target framework.

Setting	Value
Build command	`dotnet publish -c Release -o bin/publish`
Output directory	`bin/publish/wwwroot`

The CLI detects Blazor WebAssembly from a .csproj at the project root that uses the Microsoft.NET.Sdk.BlazorWebAssembly SDK, and needs the .NET SDK installed to run the build. Server-hosted Blazor apps need a server, so deploy them with Magic Containers instead.

Deploy your site

Bunny CLI
Manually

bunny sites is in Public Preview and available only in the Bunny CLI. It’s in active development, so commands, flags, and behaviour may change. Share feedback on Discord. The storage zone and pull zone behind each site appear in the dashboard under Storage and CDN.

Install the Bunny CLI and log in

curl -fsSL https://cli.bunny.net/install.sh | sh
bunny login

See Installation for npm and other options.

Create a site

From your project root, run:

bunny sites create my-site

Replace my-site with a name for your site. The CLI creates a storage zone for your files and a pull zone to serve them, then links this directory to the new site. The site is served at a b-cdn.net address, and the CLI prints the URL.

Build and deploy

bunny sites deploy --build

The CLI runs the build command, uploads the output directory from the table above, and publishes it. Every deploy is kept, so you can roll back with bunny sites deployments publish --previous.

Deploy on every push (optional)

bunny sites ci init

This writes a GitHub Actions workflow to .github/workflows/bunny-sites.yml that deploys the site on every push to main. Add your API key to the repository as a BUNNYNET_API_KEY secret. The CLI offers to run gh secret set BUNNYNET_API_KEY for you.

Build your site

From your project root, run dotnet publish -c Release -o bin/publish. The build writes your site to the output directory listed in the table above.

Create a storage zone

In the bunny.net dashboard, go to Storage and click Add Storage Zone. Give it a name, pick the main region closest to your audience, and click Add Storage Zone.

Upload your files

Open the storage zone’s file manager and upload the contents of your output directory to the root of the zone. To script uploads, use the Storage HTTP API.

Create a pull zone

Go to CDN and click Add Pull Zone. Set Origin Type to Storage Zone, select the zone you created, and click Add Pull Zone.Your site is live at https://<pull-zone-name>.b-cdn.net.

Client-side routing

Single-page apps handle routing in the browser, so a direct visit to a path like /settings needs to load index.html. The Bunny CLI turns this on for you when it detects a single-page app, unless your build includes a 404.html. To change it, set "spa" in the sites block of bunny.jsonc, or pass --spa or --no-spa to bunny sites deploy. For a manual deploy, open your storage zone’s Error handling page, set 404 File path to /index.html, and check Rewrite 404 to 200 status code. See Storage zone settings for details.

Add a custom domain

With the Bunny CLI, add the domain to your site:

bunny sites domains add example.com

The CLI prints the CNAME record to create with your DNS provider. Once the record resolves, issue a free certificate with bunny sites domains ssl example.com. For a manual deploy, add the hostname to your pull zone by following Custom hostnames.

Documentation

Features

Manage Files & Objects

Guides

Reference

Deploy Blazor WebAssembly to Bunny Storage

Deploy your site

Client-side routing

Add a custom domain

​Deploy your site

​Client-side routing

​Add a custom domain

Deploy your site

Client-side routing

Add a custom domain