Skip to content

docs: plan on Workers Paid for an in-process install too #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
danielmlr merged 1 commit into from
Oct 6, 2026
Merged

docs: plan on Workers Paid for an in-process install too #30

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/workers-paid-note.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading