Cloudflare Workers deployment

Build and deploy ProbeHarbor to Cloudflare Workers with the Astro adapter, wrangler config, and edge hosting for pages plus APIs.

Close-up of white Cat-5e Ethernet cables with RJ45 connectors
Probe JSON usually leaves the LAN over Ethernet or a nearby relay, not the public internet directly. Photo: DiscDepotDundee.co.uk. CC BY-SA 4.0

This site targets Cloudflare Workers/Pages via the Astro adapter so HTML and API routes run at the edge close to visitors. Probe fetch latency improves versus a single-region VPS for a globally readable demo.

Deployment considerations

  1. Environment variables for Supabase and Stripe live in Cloudflare dashboard secrets.
  2. Fetch timeouts to residential feed URLs must tolerate slow home uplinks.
  3. Cron or scheduled triggers may drive history inserts.

Caching interaction

Do not cache authenticated dashboard HTML at the CDN edge. Public home page caching should respect how fresh probes need to be, often aligned with Redis TTL upstream.

Reliability for users

Edge hosting is a trust signal, not a substitute for measured health. ProbeHarbor publishes cron and ingest status on system status (with optional email on degradation). Platform-wide Cloudflare incidents are tracked at cloudflarestatus.com: we do not repackage Cloudflare’s SLA as a ProbeHarbor uptime percentage.

Alternatives

Comparing full-stack options covers Node hosting versus edge Astro.