Deploy a Blazor Site
Creating a new Blazor WASM project
There are two types of Blazor projects, Blazor Server applications, which run on the server, and Blazor WASM (WebAssembly), which run in the browser. Since Blazor Server is not static, this guide will use Blazor WASM. Create a new Blazor WASM application by running:
$ dotnet new blazorwasm my-blazor-project
Creating the build script
To deploy, Cloudflare Pages will need a way to build the Blazor project. In the project's directory root, create a
build.sh file. Populate the file with this:
#!/bin/shcurl -sSL https://dot.net/v1/dotnet-install.sh > dotnet-install.shchmod +x dotnet-install.sh./dotnet-install.sh -c 5.0 -InstallDir ./dotnet5./dotnet5/dotnet --version./dotnet5/dotnet publish -c Release -o output
Creating a GitHub repository
$ dotnet new gitignore$ git init$ git add -A$ git commit -m "Initial commit"$ git remote add origin https://github.com/yourgithubusername/githubrepo.git$ git branch -M main$ git push -u origin main
Deploying with Cloudflare Pages
You can deploy your site to Cloudflare Pages by going to the dashboard, and creating a new site. Select your new GitHub repository that you created above, and in the configuration section, provide the following information:
After configuring your site, you can begin your first deploy. You should see Cloudflare Pages installing
dotnet, your project dependencies, and building your site, before deploying it.
After deploying your site, you will receive a unique subdomain for your project on
Every time you commit new code to your Blazor site, Cloudflare Pages will automatically rebuild your project and deploy it. You will also get access to on new pull requests, so you can preview how changes look to your site before deploying them to production.