Repository navigation
docs(sensitive): Miniflux and Memos as deployed on trinity (#147, #145) - #735
Merged
Merged
Conversation
The architecture row, the roadmap's Tier extras entries and the stack README said "authored, not yet deployed". Both went out on 2026-09-29 in one make up, with all sixteen containers healthy. Both host overrides resolve, and both names answer 200 through Caddy on tier-CA leaves. The changelog gets a new entry that corrects the two below it, rather than an edit to them. It records the sentinel clash #734 fixed, and why Memos ended up as ADR-0059. Still open: committing the encrypted secrets file with Miniflux's keys, and closing Memos registration at first login. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ployed-docs # Conflicts: # docs/architecture.md # docs/changelog.md # docs/roadmap.md
…ployed-docs # Conflicts: # docs/architecture.md
Gerrrt
added a commit
that referenced
this pull request
Sep 29, 2026
Main recorded the Miniflux and Memos deploys (#735). Both changelog entries are kept, main's first. The architecture row is main's, with only Stirling-PDF's "authored and not yet deployed" changed to "deployed 2026-09-29". make validate passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Sep 29, 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.
What changed
The docs now describe Miniflux and Memos as they run on trinity: deployed 2026-09-29, host overrides in place, no real data yet. Nothing runs differently.
Why
docs/architecture.md,docs/roadmap.mdandstacks/sensitive/README.mdsaid both services were "authored, not yet deployed". The changelog is never rewritten, so it gets a new dated entry that corrects the earlier two. The entry also records the sentinel clash fixed in #734, and why Memos is ADR-0059.Blast radius
Docs only.
secrets/*.sops.yamlVerification
make validatepasses.make up STACK=sensitivereported 16 of 16 services healthy.memos.matrix.elysiumandminiflux.matrix.elysiumboth resolve to10.0.99.40and return 200 through Caddy on tier-CA certificates../18/miniflux.backup-volumes.sh --inventorylists both new volumes and exits 0.disallowUserRegistrationreadsfalse).secrets/sensitive.sops.yamlwith Miniflux's keys is not committed.🤖 Generated with Claude Code