Skip to content

docs(quest): add R2 output bucket setup to the kix.quest deploy #143

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kixelated merged 2 commits into from
Oct 19, 2026
Merged

docs(quest): add R2 output bucket setup to the kix.quest deploy #143

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
228db20
docs(quest): add R2 output bucket setup to the kix.quest deploy
kixelated Oct 19, 2026
cff9c60
docs(quest): make the deploy's R2 step depend on #142
kixelated Oct 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions quest/m0/kix/deploy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,11 @@ delivery. Follow the Deployment section of `cloudflare/README.md` and steps 1,
git and agent worktrees.
- Apply the D1 migrations, including `0002_github.sql`, with
`bun run wrangler d1 migrations apply DB --remote` before deploying.
- Once raw output retention (#142) merges, create the `quest-output` R2
bucket and its 30-day `output/` lifecycle rule before deploying, as #142
adds to the README's Deployment section, and confirm the rule with
`bun run wrangler r2 bucket lifecycle list quest-output`. Until then,
`main` has no R2 binding and needs no bucket. Decided 2026-10-18.
- Add the `kix.quest` zone to the Worker's Cloudflare account. Keep the
Worker name, D1 database ID, and `AUTH_SECRET`; do not create a new
production database.
Expand Down
Loading