Zeabur

Zeabur auto-detects your framework and deploys from Git. pageflare integrates by overriding the build command to add a post-build optimization step.

How It Works

Override Zeabur’s build command in the dashboard to run pageflare after your framework’s build.

Step 1 — Install pageflare

npm install -D @pageflare/cli

Step 2 — Configure the Build

In the Zeabur dashboard, go to your service settings and set the Build Command to:

npm run build && npx @pageflare/cli dist/ --in-place --no-progress

Set the Output Directory to dist/ (or your framework’s output directory).

Step 3 — Pro License

In the Zeabur dashboard, go to your service’s Variables tab and add:

• Key: PAGEFLARE_LICENSE
• Value: your license key

Step 4 — Verify

After deploying, check the build logs in the Zeabur dashboard for the pageflare summary:

  Done  145.2 KB saved (38.1%)  1.2s
  Files  42 total, 38 optimized, 4 unchanged, 0 errors

Framework Output Directories

Framework	Output directory
Astro	dist/
Next.js static export	out/
Hugo	public/
Vite	dist/
Eleventy	_site/

Troubleshooting

Build command not used Zeabur may auto-detect a different build command. Set it explicitly in the dashboard to override.

pageflare processes 0 files The output directory doesn’t match where your framework writes output. Check the table above and update the path in the build command.