@pithy-sh/email 0.1.0

package/src/workflows/wrangler.jsonc

@@ -0,0 +1,75 @@
+{
+  // The prebuilt email worker. Like the secrets manager, this is a TEMPLATE, not a wrangler env-stanza
+  // file: staging and prod are genuinely separate workers. `pithy add email` resolves this into
+  // one complete config per environment — filling the `<...>` placeholders — and deploys each with
+  // `wrangler deploy --config <resolved>`. The user authors none of it. It hosts the send and scheduler
+  // Workflows and the every-minute scheduler cron, and holds the `send_email` binding that actually sends.
+  // Resolved per project and env → <project>-staging-email / <project>-prod-email. Worker script
+  // names are account-scoped, so the project segment is what stops a second Pithy project's deploy
+  // overwriting this one's running worker instead of colliding with it.
+  "name": "pithy-email",
+  "main": "./worker.ts",
+  // The compatibility date every Worker in this repository runs on. Stated once in the repository
+  // root's `compatibility.ts` and copied here because JSONC cannot import it —
+  // `cli/src/ci/compatibilityDates.test.ts` fails on any Worker older than it.
+  "compatibility_date": "2026-06-01",
+  "compatibility_flags": ["nodejs_compat"],
+
+  // No public URL. The callback routes (click/open/unsubscribe) and the inbound bounce handler live in
+  // the app worker; this worker is reached only by Workflow dispatch and its cron.
+  "workers_dev": false,
+
+  // The app database — the email tables (pithy_email_jobs/events/suppressions) live here, alongside the
+  // app's own data. Plus the secrets database, read for the link-signing key.
+  "d1_databases": [
+    { "binding": "DB", "database_name": "pithy-app", "database_id": "<filled-at-provision>" },
+    // The durable suppression database — one per PROJECT, shared across that project's environments,
+    // so an unsubscribe or hard bounce applies everywhere the project sends from. The same database id
+    // is bound in every environment; the name resolves to <project>-global-email-suppressions.
+    {
+      "binding": "EMAIL_SUPPRESSIONS",
+      "database_name": "pithy-email-suppressions",
+      "database_id": "<filled-at-provision>"
+    },
+    { "binding": "SECRETS", "database_name": "pithy-secrets", "database_id": "<filled-at-provision>" }
+  ],
+
+  // The Cloudflare Email Service send binding — the only thing in the kit that puts a message on the
+  // wire. `remote` is deliberately NOT written here: `resolveEmailConfig` adds it, because the
+  // resolver can only ever add the flag and a hardcoded `true` could never be turned off again. Real
+  // delivery is the default in every environment, including `dev`, where `remote: true` runs the
+  // Worker locally and sends through the service for real. `email({ devDelivery: "simulator" })`
+  // selects the local simulator instead; a deployed worker ignores the flag either way.
+  "send_email": [{ "name": "EMAIL" }],
+
+  // The master key for decrypting the link-signing secret, read through the secretsStore accessor.
+  "secrets_store_secrets": [
+    {
+      "binding": "SECRETS_ENCRYPTION_KEYS",
+      "store_id": "<filled-at-provision>",
+      "secret_name": "<filled-at-provision>"
+    }
+  ],
+
+  // The two Workflows this worker hosts. EMAIL_SENDER is the dispatch target for both immediate sends
+  // (from the app worker) and the scheduler's fan-out batches; EMAIL_SCHEDULER is fired by the cron.
+  "workflows": [
+    { "binding": "EMAIL_SENDER", "name": "pithy-email-send", "class_name": "EmailSendWorkflow" },
+    { "binding": "EMAIL_SCHEDULER", "name": "pithy-email-schedule", "class_name": "EmailSchedulerWorkflow" }
+  ],
+
+  // The every-minute scheduler cron. Cheap: scheduled() fires the scheduler Workflow, which sends
+  // nothing when nothing is due.
+  "triggers": { "crons": ["* * * * *"] },
+
+  "vars": {
+    // The full brand theme as one JSON blob (the resolved EmailTheme), filled from the app's
+    // email() config at provision. The worker parses + validates it; absent falls back to the default.
+    "EMAIL_THEME": "<filled-at-provision>",
+    "BASE_URL": "<filled-at-provision>", // the app worker's public URL, for callback links
+    "ENVIRONMENT": "<filled-at-provision>", // stamped on each send (X-Pithy-Env) so the single inbound worker can route
+    "LINK_TTL_DAYS": "90",
+    "MAX_ATTEMPTS": "5",
+    "SCHEDULER_ENABLED": "true"
+  }
+}