Skip to main content
Docusaurus builds a static HTML page for every doc and blog post into build.

​
Configure Docusaurus

Set url and baseUrl in docusaurus.config.js to match where the site is served, for example url: "https://docs.example.com" and baseUrl: "/". Leave trailingSlash unset, or set it to true. With false, Docusaurus writes about.html and links to /about, which returns a 404.

​
Deploy your site

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.
1

Install the Bunny CLI and log in

See Installation for npm and other options.
2

Create a site

From your project root, run:
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.
3

Build and deploy

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.
4

Deploy on every push (optional)

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.

​
Add a custom domain

With the Bunny CLI, add the domain to your site:
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.
Last modified on October 15, 2026