From db344cd515e8be6e4057323a9a81a0237e95eee5 Mon Sep 17 00:00:00 2001 From: Daniel Date: Tue, 6 Oct 2026 17:18:14 +0200 Subject: [PATCH] docs: plan on Workers Paid for an in-process install too The README only named Workers Paid for sandboxed installs. An in-process install serves its pages on Workers Free, but the scheduled sync most likely exceeds Free's 10 ms CPU limit per Cron Trigger (untested). Patch changeset: 0.3.1. Its Version Packages run is the first automated registry release since releases.emdashcms.com stopped failing with PROFILE_FETCH_FAILED. --- .changeset/workers-paid-note.md | 5 +++++ README.md | 5 +++++ 2 files changed, 10 insertions(+) create mode 100644 .changeset/workers-paid-note.md diff --git a/.changeset/workers-paid-note.md b/.changeset/workers-paid-note.md new file mode 100644 index 0000000..48e1b97 --- /dev/null +++ b/.changeset/workers-paid-note.md @@ -0,0 +1,5 @@ +--- +"@eisbachcode/emdash-plugin-analytics": patch +--- + +The README now says to plan on Workers Paid on Cloudflare for an in-process install too: the pages work on Workers Free, but the scheduled sync will most likely exceed Free's 10 ms CPU limit per Cron Trigger. No code changes from 0.3.0. diff --git a/README.md b/README.md index af3da69..84bade4 100644 --- a/README.md +++ b/README.md @@ -192,6 +192,11 @@ To run it sandboxed, list it under `sandboxed: [analytics]` instead. That needs a sandbox runner, which on Cloudflare means the Workers Paid plan; see EmDash's [plugin sandbox guide](https://docs.emdashcms.com/deployment/plugin-sandbox/). +On Cloudflare, plan on Workers Paid either way. Installed under `plugins`, +the pages and the widget work on Workers Free, but the scheduled sync runs +under Free's 10 ms CPU limit per Cron Trigger and will most likely be cut +off. This has not been tested on Free. + ## Settings Fill these in under Plugins → Analytics → Settings.