Skip to documentation
MMirageDocs

Execution

Cloudflare runners

Run explicit Docker-free Linux jobs in shared or BYO Cloudflare accounts.

When to use Cloudflare

Cloudflare is a separate, explicit Linux execution path. A direct mirage-cloudflare-* label never enters Local Mac's retry policy and never silently moves between shared and BYO billing accounts.

Cloudflare job
jobs:
  test:
    runs-on: mirage-cloudflare-standard-3
    steps:
      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
        with:
          node-version: 24
      - run: npm test

Labels

Presets range from mirage-cloudflare-lite through mirage-cloudflare-standard-4. The mirage-cloudflare-ubuntu-latest alias selects standard-3.

mirage-cloudflare-vcpu:<1..4>-memory_mib:<n>-disk_mb:<n>

A job must select exactly one Cloudflare profile.

Limitations

  • Linux x64 only for provider experiments.
  • No Docker commands, Docker container actions, service containers, or job containers.
  • JavaScript and composite actions are supported.
  • Artifacts and results remain on GitHub; the Actions cache is stored in R2.
  • The repository must be private, trusted, unarchived, and explicitly opted in.

Experiments

An adapted Linux x64 job can compare Cloudflare with GitHub Actions and Local Mac. Mirage pins the experiment to the authoritative source SHA and rechecks repository, permissions, entitlement, and backend health immediately before dispatch.