Cleavr
Cleavr provisions and manages servers with Git-based deployments. pageflare integrates as part of the deployment hook — optimize your site after the build step on the provisioned server.
How It Works
Section titled “How It Works”Add pageflare to Cleavr’s deployment hooks. The build hook runs after your framework builds the site, and pageflare optimizes the output before Cleavr activates the new deployment.
Step 1 — Install pageflare on the Server
Section titled “Step 1 — Install pageflare on the Server”In Cleavr’s deployment hooks, add a Build hook:
curl -fsSL https://get.appz.dev/pageflare/install.sh | shOr if Node.js is available:
npm install -g @pageflare/cliStep 2 — Configure the Deployment Hook
Section titled “Step 2 — Configure the Deployment Hook”Add a hook after your build step:
Hook type: Build Script:
cd {{ releasePath }}npm run buildpageflare dist/ --in-place --no-progressReplace dist/ with your framework’s output directory.
Step 3 — Pro License
Section titled “Step 3 — Pro License”In Cleavr, go to your site’s Environment settings and add:
- Key:
PAGEFLARE_LICENSE - Value: your license key
Step 4 — Verify
Section titled “Step 4 — Verify”Check the deployment logs in Cleavr for the pageflare summary:
Done 145.2 KB saved (38.1%) 1.2s Files 42 total, 38 optimized, 4 unchanged, 0 errorsFramework Output Directories
Section titled “Framework Output Directories”| Framework | Output directory |
|---|---|
| Astro | dist/ |
| Next.js static export | out/ |
| Hugo | public/ |
| Vite | dist/ |
| Eleventy | _site/ |
Troubleshooting
Section titled “Troubleshooting”pageflare not found Make sure the install hook runs before the optimization hook. If using npm, ensure Node.js is available on the server.