Skip to content

Document tls internal hot-reload behavior#55

Open
chrislearn wants to merge 1 commit into
mainfrom
chris/docs-tls-internal-reload
Open

Document tls internal hot-reload behavior#55
chrislearn wants to merge 1 commit into
mainfrom
chris/docs-tls-internal-reload

Conversation

@chrislearn
Copy link
Copy Markdown
Member

Summary

Follow-up to #54: document the tls internal reload story.

The fix commit on #54 made two changes:

  1. Gate the global tls { internal } fallback so it only kicks in when ACME is not configured.
  2. Make the resolver's local_ca swappable and global_internal atomic, so a hot reload can bootstrap the local CA mid-run when a site flips to tls internal.

(1) was already promised in the docs (the original PR text said "The global form only takes effect when ACME is not configured") — the fix just made the code match. (2), on the other hand, is a new user-visible reload behavior that was never documented. This PR fixes that.

  • en: Add a Local CA (tls internal) bullet to the existing Hot Reload section in docs/en/tls-and-acme.md.
  • zh: Add a ### 热重载行为 subsection inside the 本地 CA section in docs/zh/tls-and-acme.md, since the Chinese doc does not have a top-level Hot Reload section.

Test plan

  • Docs-only change; no code touched.

🤖 Generated with Claude Code

The previous PR shipped resolver fixes for the ACME-gating rule and the
ability to bootstrap the local CA mid-run on reload, but only the
ACME-gating rule was already mentioned in the docs (it was the
documented intent — the fix just made the code match). The reload
story for `tls internal` was not covered.

- en: Add a `tls internal` bullet to the existing Hot Reload section.
- zh: Add a `### 热重载行为` subsection inside the 本地 CA section,
  since the Chinese doc does not have a top-level Hot Reload section.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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