Repository navigation
feat(krater): get production ready for the approval pipeline - #73
Merged
Merged
Conversation
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]>
This was referenced Nov 5, 2026
2 of 3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.nixstaysenable = false.hosts/weft/krater.nix: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.secrets/krater-env.ageandsecrets/central-prod-krater.age: rewritten bybin/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 tojspandweftonly.nixosConfigurations.weft.config.system.build.toplevelevaluates.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):
https://krater.patchworklabs.org/auth/callbackopenid profile email groups roles slack directoryreviewerfor the Ganymede Reviewer group,adminfor the Ganymede Admin groupcd secrets && agenix -e krater-env.ageand setKRATER_WEAVE_CLIENT_SECRET.jaspermayone/infratailscale/policy.hujson, givetag:patchwork-krateraccess topw-skein:5432again. The grant and test lines are in feat(krater): krater staging on weft, production ready behind one switch #32's body.enable = trueinhosts/weft/krater-production.nix.kraterrole. Then deploy weft and runsystemctl start krater-prod-buildon it.kraterandkrater-storage(patchworklabsorg/dns), then bumppatchwork-infrainjaspermayone/infraand deploy alastor.https://krater.patchworklabs.org/healthzand/healthz/workerreturn 200. Add outside uptime checks on both, every 5 minutes. The worker can't report its own death.