DeployHQ
DeployHQ automates deployments from Git repositories. pageflare integrates as a build command in DeployHQ’s build pipeline — optimize your site before DeployHQ transfers files to your server.
How It Works
Section titled “How It Works”Add pageflare to DeployHQ’s build commands. DeployHQ runs these commands after pulling your repository and before deploying files.
Step 1 — Configure Build Commands
Section titled “Step 1 — Configure Build Commands”In your DeployHQ project, go to Build Commands and add:
npm cinpm run buildnpx @pageflare/cli dist/ --in-place --no-progressSet the Repository subdirectory to your project root and the Deployment subdirectory to your framework’s output directory (e.g., dist/).
Step 2 — Pro License
Section titled “Step 2 — Pro License”In DeployHQ, go to your project’s Environment Variables and add:
- Key:
PAGEFLARE_LICENSE - Value: your license key
Step 3 — Verify
Section titled “Step 3 — Verify”After deploying, check the build log in DeployHQ 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”Build commands fail Make sure DeployHQ’s build environment has Node.js installed. Check that the Node.js version is 20 or later.