{
	"$schema": "node_modules/wrangler/config-schema.json",
	"name": "accounts",
	"main": "src/accounts.app.ts",
	"compatibility_date": "2026-06-16",
	"compatibility_flags": ["nodejs_compat"],
	// Shared `recflare` D1 database. The `accounts` table schema/migrations are owned
	// by the `auth` worker; this worker binds it read/write to look up and create
	// accounts. The "local" placeholder is replaced with the real id from RECFLARE_D1
	// (see .env) at deploy time.
	"d1_databases": [
		{
			"binding": "DB",
			"database_name": "recflare",
			"database_id": "local"
		}
	],
	// Cross-worker binding to the SignalR notifications hub DO (owned/migrated by
	// the `notify` worker). We only invoke its RPC methods; no migration here.
	"durable_objects": {
		"bindings": [
			{
				"name": "RECFLARE_NOTIFICATIONS_HUB",
				"class_name": "NotificationsHub",
				"script_name": "notify"
			}
		]
	},
	"logpush": false,
	// Shared Secrets Store holding the HS256 JWT signing key. Every worker binds the
	// same store as JWT_SECRET so tokens signed by `auth` verify here. The "local"
	// store_id placeholder is replaced with RECFLARE_SECRETS_STORE at deploy time.
	"secrets_store_secrets": [
		{
			"binding": "JWT_SECRET",
			"store_id": "local",
			"secret_name": "JWT_SECRET"
		}
	],
	// Cloudflare Email Sending, for the code that confirms an email change
	// (POST /account/me/email). Nothing to splice in: the binding has no id, but the `from`
	// domain (EMAIL_FROM, default no-reply@<DOMAIN>) has to be enabled for Email Sending once
	// per account — see DEPLOYING.md. Locally (and under vitest) the binding logs the message.
	"send_email": [
		{
			"name": "EMAIL"
		}
	],
	"upload_source_maps": true,
	"observability": {
		"enabled": false
	},
	"vars": {
		"ENVIRONMENT": "development", // overridden during deployment
		"SENTRY_RELEASE": "unknown", // overridden during deployment
		// Overridden at deploy time, same as `auth`. The confirmation email's link is built
		// from these (`https://www.<DOMAIN>/confirm-email`).
		"DOMAIN": "rec.example.com",
		"SUBDOMAINS": "{}"
	}
}