Skip to content

feat(krater): get production ready for the approval pipeline - #73

Merged
jaspermayone merged 4 commits into
mainfrom
claude/krater-production-rev
Nov 6, 2026
Merged

jaspermayone merged 4 commits into
mainfrom
claude/krater-production-rev

Conversation

@Adambomb210

@Adambomb210 Adambomb210 commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator

Gets Krater production ready to turn on, with only the approval pipeline: proposals, review, budget grants, project Slack channels and the gallery. Krater Compute stays off (compute.enable = false), so no Vast account is used. This PR doesn't turn production on: hosts/weft/krater-production.nix stays enable = false.

  • hosts/weft/krater.nix:
    • Production's first build is Krater main 9673bbe (2026-11-03), after staging ran the whole proposal, amendment and completion flow live. The old fallback, b081a13 (Oct 22), predated the launch hardening and every fix since.
    • The Slack feed and alerts channel ids for the Ganymede Review app in the Patchwork workspace. They aren't secret.
  • secrets/krater-env.age and secrets/central-prod-krater.age: rewritten by bin/new-krater-secrets production, with a new database password, secret key and storage keys, plus the app's bot token and signing secret. Production has never run, so nothing used the old files. Both are still encrypted to jsp and weft only.

nixosConfigurations.weft.config.system.build.toplevel evaluates.

Still empty: KRATER_WEAVE_CLIENT_SECRET. Adam can't open Weave production, so Krater won't start until it's set.

Order, all yours (@jaspermayone):

  1. On Weave production, check Krater's app:
    • Redirect URI https://krater.patchworklabs.org/auth/callback
    • Scopes openid profile email groups roles slack directory
    • Access: everyone
    • Roles: reviewer for the Ganymede Reviewer group, admin for the Ganymede Admin group
  2. On this branch, run cd secrets && agenix -e krater-env.age and set KRATER_WEAVE_CLIENT_SECRET.
  3. In jaspermayone/infra tailscale/policy.hujson, give tag:patchwork-krater access to pw-skein:5432 again. The grant and test lines are in feat(krater): krater staging on weft, production ready behind one switch #32's body.
  4. Merge this PR, then set enable = true in hosts/weft/krater-production.nix.
  5. Deploy skein, which creates the krater role. Then deploy weft and run systemctl start krater-prod-build on it.
  6. Merge the DNS PR for krater and krater-storage (patchworklabsorg/dns), then bump patchwork-infra in jaspermayone/infra and deploy alastor.
  7. Check https://krater.patchworklabs.org/healthz and /healthz/worker return 200. Add outside uptime checks on both, every 5 minutes. The worker can't report its own death.

Adambomb210 and others added 2 commits November 3, 2026 17:09
Production has no CI deploy, so `systemctl start krater-prod-build` builds the fallback rev. b081a13 (Oct 22)
predates Krater's launch hardening, the OSPool funder packet, the any-member change and every fix since;
9673bbe is main after staging ran the whole proposal, amendment and completion flow live, plus the gallery's full
Markdown and hosted images (deployed to staging the same day). Production stays off.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
secrets/krater-env.age and secrets/central-prod-krater.age are written again by
bin/new-krater-secrets production (new database password, secret key and
storage keys), now with the bot token and signing secret of the Ganymede
Review app in the Patchwork workspace. Production has never run, so nothing
used the old files. KRATER_WEAVE_CLIENT_SECRET is still empty: Jasper fills
it in with `cd secrets && agenix -e krater-env.age`.

The feed and alerts channel ids go in the host file; they aren't secret.
Production stays off (enable = false).

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@jaspermayone
jaspermayone merged commit c321079 into main Nov 6, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants