Files
document-haness/docs/keycloak-session-store/final/assets/renewal-to-serving-gap/renewal-to-serving-gap.mmd
T
DongHyeonkaandClaude Opus 5 b2963105a8 docs(keycloak-session-store): import the session-storage lab as a new project
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.

Follows the import procedure in README.md.

  source/     the originating repository verbatim — 78 documents, 28 SVGs,
              8 manifests, plus .source-revision recording the commit
  final/      the SSOT
    document.md   729 lines written from the 29 experiment documents, not
                  concatenated: what was predicted, what was measured, and
                  where the measurement itself was wrong
    evidence/raw    125 outputs, flattened to <experiment>__<file> because
                    the originals collided (01-baseline.txt appeared three
                    times) and the audit only globs the top level
    evidence/meta   one per raw file; command and exitCode are null and the
                    README says why rather than inventing them
    evidence/browser  22 captures
    assets/       three diagrams through techviz
    .techviz/     their VizSpecs

A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.

Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.

verify-pipeline.py passes. audit-records.py reports no issues.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-04 22:51:59 +09:00

12 lines
448 B
Plaintext

%% 인증서 갱신이 서빙에 닿기까지
%% question: certbot 이 갱신에 성공한 뒤 nginx 가 새 인증서를 서빙하기까지 무엇이 필요한가
flowchart LR
n0["certbot renew"]
n1[("live/fullchain.pem")]
n2["renewal-hooks/deploy"]
n3["nginx 워커"]
n0 -->|"새 인증서 기록"| n1
n1 -->|"reload 없이는 닿지 않는다"| n3
n0 -->|"갱신 성공 시 호출"| n2
n2 -->|"reload 신호"| n3