Repository navigation
Docs: move roots list instructions to a Deployment subsection - #68
Merged
Merged
Conversation
Generating, publishing and configuring a roots list is a deployment task, so describe it in a new "Accepted roots" subsection under Deployment, with how to configure the roots URL and check it with the resubmission check, and link to it from root-not-accepted. Also name the example lists after their header. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Summary
npm run roots-hashescommand, the list format and example (moved fromroot-not-accepted), and new guidance on publishing the list on another hostname (preferably outside the zone), configuring its URL inCONFIG.logEnvironments, checking it with the resubmission check, and regenerating it when the log's roots change.root-not-acceptedkeeps what the check does, when it's made, why roots can't come from the log itself, and how it behaves at runtime, linking to the new subsection; the other references link to it too.accepted-roots.txtfor a list shared by several logs, andtiger2027h1-accepted-roots.txtfor one log's list.All internal links resolve.