Skip to content

Docs: move roots list instructions to a Deployment subsection - #68

Merged
robstradling merged 1 commit into
mainfrom
readme-accepted-roots
Nov 16, 2026
Merged

robstradling merged 1 commit into
mainfrom
readme-accepted-roots

Conversation

@robstradling

Copy link
Copy Markdown
Member

Summary

  • Add an "Accepted roots" subsection under Deployment (and to the contents), with the npm run roots-hashes command, the list format and example (moved from root-not-accepted), and new guidance on publishing the list on another hostname (preferably outside the zone), configuring its URL in CONFIG.logEnvironments, checking it with the resubmission check, and regenerating it when the log's roots change.
  • root-not-accepted keeps 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.
  • Name the example lists after their header: accepted-roots.txt for a list shared by several logs, and tiger2027h1-accepted-roots.txt for one log's list.

All internal links resolve.

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>
@robstradling
robstradling merged commit 0d4941a into main Nov 16, 2026
17 checks passed
@robstradling
robstradling deleted the readme-accepted-roots branch November 16, 2026 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant