面向 HTTP、DNS、TLS、Caddy、SSH、发布与恢复的可复现 runbooks。每条笔记把公共标准或厂商手册转成一个小流程，并留下可追溯的来源。
Independent operations notebook
为可靠 Web 服务而写的可视化现场笔记
26
source-backed notes
32
working topics
0
browser scripts
- Source commit
7f66e47- Built at
This page reports the commit and build time of the exact artifact being served, making the release reproducible against the source tree.
Choose a starting point
Three useful ways in
The notes are short by design. Pick the boundary closest to the work in front of you.
01
Operate the edge
Start with the public boundary: roots, headers, caching, and the certificate a visitor actually receives.
Read 静态服务器应有一个明确的根目录
02
Release with evidence
Build, verify, publish, and inspect a representative route before replacing the known-good artifact.
Read 静态网站的发布检查清单
03
Recover without guessing
Keep backups, restart limits, and host identity close enough to rehearse before an incident.
Read 备份只有在演练过恢复之后才有用Follow a complete path
Three field-note series
Each series groups a boundary into a compact route. Start with the question you need to answer, then move through the evidence.
Browse the index
Follow a topic across the notes
Tags are maintained from the article front matter, so each route stays tied to actual material.
Operator kit
Small files, ready to inspect
Plain-text checks and examples that stay useful without an account, package manager, or browser runtime.
Latest notes
Recent field work
Concrete procedures, public references, and small artifacts you can inspect before adapting them.
事故复盘应留下一份事实记录
复盘是一张从检测到症状到验证修复的顺序图，由产生每个事实的命令支撑。
用两条命令读取公共边缘
两个小的只读 helper 把公共端点变成发布前和发布后都能检查的证据。
CAA 记录应授权你实际使用的签发者
CAA 收窄了证书签发策略，但一条错误的记录会像过期证书一样有效地阻断续期。
Content-Type 应描述你实际发送的字节
文件名只是一个提示，响应头才是面向浏览器的表示契约。
Cookie 作用域应比应用边界更窄
发送给过多主机或路径的 Cookie，会放大这些边界上每个错误的冲击。
HEAD 应描述与 GET 相同的表示
HEAD 是 GET 的元数据视图；状态与表示头应讲同一个故事。
HSTS 应带着恢复计划来灰度发布
HSTS 是被缓存的浏览器策略，因此一个配置错误可能比创建它的服务器变更活得更久。
发布清单应点名每一个已发布的字节
一个聚合摘要有用，但一份排序的逐文件清单能精确告诉你什么变了或丢了。