Zerops

Zerops uses a zerops.yml file to define your build pipeline. pageflare integrates as an additional build step after your framework produces its output.

How It Works

Add pageflare to the build.run section of zerops.yml. Zerops runs the commands sequentially and deploys the output.

Step 1 — Install pageflare

Add pageflare as a dev dependency:

npm install -D @pageflare/cli

Step 2 — Configure zerops.yml

zerops.yml

zerops:
  - setup: my-site
    build:
      base: nodejs@22
      buildCommands:
        - npm ci
        - npm run build
        - npx @pageflare/cli dist/ --in-place --no-progress
      deployFiles: dist/~
    run:
      base: static

Step 3 — Pro License

Add PAGEFLARE_LICENSE to the build environment in zerops.yml:

zerops.yml

zerops:
  - setup: my-site
    build:
      base: nodejs@22
      envSecrets:
        PAGEFLARE_LICENSE: your-license-key
      buildCommands:
        - npm ci
        - npm run build
        - npx @pageflare/cli dist/ --in-place --no-progress
      deployFiles: dist/~

Or set it in the Zerops dashboard under your service’s environment variables.

Step 4 — Verify

After deploying, check the build logs in the Zerops 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	deployFiles
Astro	dist/	dist/~
Next.js static export	out/	out/~
Hugo	public/	public/~
Vite	dist/	dist/~

Troubleshooting

Build fails with “command not found” Make sure the base is set to nodejs@22 or later. The npx command requires Node.js.

pageflare processes 0 files The directory in the build command doesn’t match your framework’s output. Update both the pageflare path and deployFiles to match.