# Runbooks

Task-focused troubleshooting guides. Thin — they point at the source repos for
authoritative config and commands rather than duplicating them.

## Index

| Runbook | Covers |
|---------|--------|
| [switch-crs310.md](switch-crs310.md) | The MikroTik CRS310 switch — connectivity, VLANs, mgmt-plane lockout recovery, Ansible reconfig. |
| [publishing-services-mf01.md](publishing-services-mf01.md) | Publishing HTTP services on mf01 as `<svc>.mf01.makerfloss.eu` (VPS-terminated TLS over wg1). |

## Adding a runbook

Keep it lean. Good structure:

1. **Symptom** — what you observe.
2. **Reach** — which [access.md](../access.md) path applies.
3. **Diagnose** — concrete checks (commands, what good/bad looks like).
4. **Fix** — where the change lands (source repo + file), and the safety rules
   for applying it to live infra.
5. **Verify** — how you confirm it's actually fixed (evidence, not assertion).
6. **Links** — source-repo specs/runbooks.