Repository navigation
docs: relay journal design and plan - #148
Merged
Merged
Conversation
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.
Design and implementation plan for the relay journal (a merged, live log of everything that passes through the relay, in
/admin/journal, kept 7 days).docs/superpowers/specs/2026-11-13-journal-relais-design.md(in French): the owner's decisions and the design.docs/superpowers/plans/2026-11-13-journal-relais.md: the implementation plan.Implementation: ReCasaOS/ReCasaOS-Relay
feat/relay-journal. During implementation, Caddy's access log moved from a file to the compose network (enrolment writes it with the same daily rotation) and refused connections are summarised per address; the relay'sdocs/self-hosting.mddescribes what was built.