Repository navigation
feat: add krater and krater-storage.patchworklabs.org for production - #18
Merged
jaspermayone merged 1 commit intoNov 6, 2026
Conversation
Krater production (Project Ganymede portal) and its screenshot storage, on weft behind alastor's edge like krater-staging (patchworklabsorg#17). Replaces patchworklabsorg#12, whose branch predates patchworklabsorg#17 and conflicts with it. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This was referenced Nov 5, 2026
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.
Adds the two hostnames for Krater production, the Project Ganymede portal. Both are A records for alastor (129.213.163.213), proxied through Cloudflare like staging's:
krater.patchworklabs.org: the portal (Weave production sign-in).krater-storage.patchworklabs.org: its S3 storage on weft (gallery screenshots while Compute is off). No cache or Rocket Loader rule may apply to it, because they break S3 signatures.They're one level under
patchworklabs.org, so Cloudflare's edge certificate covers them. They serve only once Krater production is on (patchworklabsorg/infra#73). Merge this as step 6 there, before alastor's routes are deployed.This replaces #12. That branch conflicts with main since #17 added the staging records separately, so this one starts from main with only the production records. #12 can be closed.
The branch is up to date with
main, and the keys are in alphabetical order as octoDNS needs.octodns-validate,check_zonesand the tool tests pass.🤖 Generated with Claude Code