You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-6Lines changed: 14 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,12 +55,13 @@ What the deploy button does not provision for you:
55
55
- GitHub App credentials
56
56
- GitHub OAuth app credentials
57
57
- Gemini API key
58
+
- Cloudflare API credentials for DLQ inspection, replay, and purge
58
59
59
60
That means the deploy flow is best thought of as "Cloudflare infrastructure bootstrap", followed by a short secrets setup step.
60
61
61
62
For this repo's own production deployment, the checked-in route and binding IDs in [`wrangler.jsonc`](/wrangler.jsonc) are intentional. They are what keep `codra.run` deploying against the same Worker, KV namespace, and queues. If you fork Codra, replace those values with your own resources.
62
63
63
-
## Required Secrets And Local DB Vars
64
+
## Required Secrets, DLQ, And Local DB Vars
64
65
65
66
Codra expects these secrets in Cloudflare production and in local `.dev.vars` for development:
66
67
@@ -70,23 +71,30 @@ Codra expects these secrets in Cloudflare production and in local `.dev.vars` fo
70
71
-`GITHUB_CLIENT_ID`
71
72
-`GITHUB_CLIENT_SECRET`
72
73
-`GEMINI_API_KEY`
74
+
-`CF_API_TOKEN`
75
+
-`CF_ACCOUNT_ID`
76
+
77
+
DLQ setup is required during installation because Codra includes `/api/dlq` inspection, replay, and purge workflows. Create or identify the dead letter queue and copy its queue ID into `CF_DLQ_ID`:
78
+
79
+
```bash
80
+
npx wrangler queues create codra-review-dlq
81
+
npx wrangler queues list
82
+
```
83
+
84
+
The Cloudflare API token must have Queues edit access for the account that owns the Worker queues. `CF_DLQ_ID` is a required environment variable, not a secret, and should point at the `codra-review-dlq` queue used by the `dead_letter_queue` consumer config in [`wrangler.jsonc`](/wrangler.jsonc).
73
85
74
86
Local development and migrations also need:
75
87
76
88
-`CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_STRING_HYPERDRIVE` for local Worker DB access
77
89
-`DATABASE_URL` for local/admin migrations
78
90
79
-
Optional, only for DLQ inspection and replay APIs:
80
-
81
-
-`CF_API_TOKEN`
82
-
-`CF_ACCOUNT_ID`
83
-
84
91
The expected local shape is already documented in [`.dev.vars.example`](/.dev.vars.example).
85
92
86
93
In the checked-in production Wrangler config, these values are regular environment vars rather than secrets:
0 commit comments