Seenode
Seenode provides Node.js hosting with Git-based deployments. pageflare integrates by customizing the build command to optimize your site’s output.
How It Works
Section titled “How It Works”Override the build command in the Seenode dashboard to run pageflare after your framework’s build.
Step 1 — Install pageflare
Section titled “Step 1 — Install pageflare”npm install -D @pageflare/cliStep 2 — Configure the Build
Section titled “Step 2 — Configure the Build”In the Seenode dashboard, set the Build Command to:
npm run build && npx @pageflare/cli dist/ --in-place --no-progressStep 3 — Pro License
Section titled “Step 3 — Pro License”In the Seenode dashboard, add an environment variable:
- Key:
PAGEFLARE_LICENSE - Value: your license key
Step 4 — Verify
Section titled “Step 4 — Verify”After deploying, check the build logs 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 processes 0 files The output directory in the build command doesn’t match where your framework writes output. Check the table above.