pr_01m47d15m3e54sn21z27rpy5n9/services/events/wrangler.jsonc

33 lines1,236 bytesCodeBlame

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

Initial g1t: services, event bus, intents and attempts1{
2 "$schema": "../../node_modules/wrangler/config-schema.json",
3 "name": "g1t-events",
4 "account_id": "1e6f2cffa3f445920836e8ebe446bb58",
5 "compatibility_date": "2026-09-26",
Agents as a team: lifecycle, merge queue, billing and a new shell6 // Runs next to its database: a request makes several queries in turn,
7 // and each would otherwise cross the distance to it.
8 "placement": { "mode": "smart" },
Events service in Rust, with RFC 3339 times and accurate push events9 "main": "build/index.js",
10 "build": { "command": "cargo install -q worker-build@0.8.7 && worker-build --release" },
Initial g1t: services, event bus, intents and attempts11 "workers_dev": false,
12 "d1_databases": [
13 {
14 "binding": "DB",
15 "database_name": "g1t-events",
16 "database_id": "dd889749-0d01-4c94-8b9b-d789dec1c0e4",
17 "migrations_dir": "migrations"
18 }
19 ],
20 "queues": {
21 "producers": [
22 { "binding": "BUS", "queue": "g1t-events" },
23 // One queue per subscribing service, so each consumes, retries
24 // and scales on its own. Bindings named SUBSCRIBER_* receive
25 // every event.
Acceptance checks in sandboxes, line comments and review verdicts26 { "binding": "SUBSCRIBER_WORK", "queue": "g1t-events-work" },
Integrations: your own model provider, alerts that open issues, tickets agents read27 { "binding": "SUBSCRIBER_RUNNER", "queue": "g1t-events-runner" },
28 { "binding": "SUBSCRIBER_INTEGRATIONS", "queue": "g1t-events-integrations" }
Initial g1t: services, event bus, intents and attempts29 ],
30 "consumers": [{ "queue": "g1t-events", "max_batch_size": 100, "max_batch_timeout": 1 }]
31 },
32 "observability": { "enabled": true }
33}