Add a Frameworks section to Edge Scripting, and the bunny sites reference

[bogdan-at-bunny]

What changed

• Adds a Frameworks group to the Edge Scripting docs, between Script Types and Deployment.
• Adds scripting/frameworks/index.mdx, which explains how a framework server runs at the edge and what constrains it.
• Adds scripting/frameworks/astro.mdx, a guide that renders Astro per request on Edge Scripting with the bunny.net adapter.
• Adds cli/commands/sites.mdx, the reference for bunny sites. It covers both shapes of site: a directory of files, and a build that renders per request.
• Adds the static layer to cdn/custom-404-page.mdx and storage/static-site-hosting/index.mdx: a deploy's own 404.html, _redirects, and _headers.
• Links the new section from the Edge Scripting index and from the frontend deployment guides.

Why

A reader who wants a framework on Edge Scripting had no page to start from. The Storage guides cover fully static sites, and stop where the dynamic part begins.

Astro is a server-first framework, so a guide that only prerenders it misses the point. An Astro build that renders per request is a (Request) => Response handler, which is the shape a script already needs.

One deploy command

An earlier revision of this branch documented a bunny deploy command beside bunny sites deploy. There is only one command now, bunny sites deploy, and it reads the build to decide what to send. So cli/commands/deploy.mdx is gone and cli/commands/sites.mdx covers both shapes. Neither page has shipped, so no redirect is needed.

Both pages also say when the adapter offer appears, which readers could not tell before: only a project that renders a page on demand is offered an adapter. A project that prerenders every page deploys as files and hears nothing about adapters.

Two things the guide got wrong

Found by running the commands again for this revision:

• The example GitHub Actions workflow deployed without building. A workflow has nobody to ask, so an unattended deploy never offers a build: it needs --build.
• --env and --env-file were shown without --build. They apply to the build, and the command reports the mistake rather than ignoring them.

Depends on the adapter package

This guide uses @bunny.net/astro-adapter. The package has to be published to npm before this merges. Until then the install command in the guide does not resolve.

The adapter is what keeps the guide short. It adds itself to the config, and it does not set output:

export default defineConfig({
  adapter: bunny(),
});

Verified

Every command in the guide was run against a real account, with the adapter installed the way a reader would install it.

• A build that renders per request produced a script of about 660 kB, against the 10 MB script limit.
• Deployed to a real site. Pages that render per request, src/pages/api/, dynamic routes, prerendered pages from Storage, hashed assets, and the build's own 404 page all answered as the guide says.
• A build with every route prerendered deployed as files, got its own preview URL, and answered a missing path with its own 404 page.
• Publishing an earlier deploy took back the page and the asset it names, together.
• Both verification sites were deleted afterwards.
• mint broken-links reports no new broken links.

One table on the bunny sites page waits on a CLI fix. It says a page may be cached for 60 seconds, which is what the router asks for. In the live run a page reached the browser with a far longer lifetime, because the router only sets Cache-Control on a response that carries none, and Bunny Storage sends one. The table describes the behaviour this documents, and the CLI change is tracked in BunnyWay/cli#172. Neither branch has shipped, so the fix can land before either merges.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NpdDkzyH7pPq5FZqPCRhzE

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
bunny	🟢 Ready	View Preview	Aug 19, 2026, 7:54 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[bogdan-at-bunny]

@mintlify deploy to staging

[mintlify]

AI credits exhausted for this billing cycle. Upgrade your plan or wait for your credits to renew.