{
// Deploying your own copy? Run `npm run setup` (or edit the domain and
// database_id below by hand) -- the values here are the upstream
// deployment's, and this file is the only config wrangler reads. It takes
// precedence over wrangler.toml silently, so editing a .toml instead has
// no effect.
//
// Committed rather than gitignored because Cloudflare Workers Builds
// clones the repo and needs the D1 binding present at build time;
// dashboard-set bindings weren't surviving into new versions. Once this
// file exists it is the source of truth for vars and bindings, so
// dashboard-only entries not listed here stop applying.
//
// No secrets here: database_id and the domain are identifiers, not
// credentials. Discord secrets still live in the dashboard
// (Settings > Variables and secrets), untouched by this file.
//
// DISPOSABLE_DOMAIN picks which mode the Worker runs in. Set it to a
// domain you own to receive mail through Email Routing. Clear it (or
// remove the line) to run on mail.tm instead: no domain, no DNS, no
// Email Routing, addresses get provisioned on mail.tm's domain and their
// API is polled on the frequent cron below. See
// docs/deploy-cloudflare-mailtm.md.
"name": "cinderbox",
"main": "src/worker.ts",
"compatibility_date": "2024-09-23",
"compatibility_flags": ["nodejs_compat"],
"vars": {
"DISPOSABLE_DOMAIN": "vsvn.net",
"ADAPTERS": "discord",
"MAX_ACTIVE_ADDRESSES": "10"
},
"d1_databases": [
{
"binding": "DB",
"database_name": "cinderbox",
"database_id": "80611409-6ad6-4226-a988-238e3d2e01fa"
}
],
// Daily cleanup, plus the mail.tm poll. The poll returns immediately