Stack patterns
Stratum-2/3 patterns with stack-specific content. More opinionated than kernel patterns — they assume my stack.
Available patterns
Section titled “Available patterns”| Pattern | Purpose |
|---|---|
| Cross-device SSH | Reach my desktop from any device on the tailnet; reattach long-running sessions |
| Tailnet browser access | Temporarily expose files or a local service across the tailnet via tailscale serve + miniserve — no public ports, browser-ready from any device |
| Image paste pipeline | ShareX → Zipline → tailnet — clipboard to shareable URL in <1s |
| Claude Code session recovery | Decision tree across claude -r <uuid> / pconv rebuild-index / pconv doctor --dump-stale when /resume shows wrong sessions |
| Dokploy on TrueNAS via VM | Run a self-hosted PaaS on a NAS appliance without fighting it — Debian VM + Tailscale handoff + Dokploy install in ~30 min |
| Tailscale HTTPS three levels | Decision framework for tailnet HTTPS — HTTP-over-tunnel vs tailscale serve vs tailscale cert + Traefik + systemd timer. Knowing where to stop saves an afternoon |
| TrueNAS stuck ZFS dataset | Diagnostic ladder for “EBUSY — dataset is busy” when nothing visible holds the dataset, plus the rename-then-destroy escape hatch |
| Debian VM tailnet bootstrap | Every-screen netinst recipe + the two installer footguns nobody warns you about (sudo, curl) + VNC-once → SSH-via-tailnet handoff |
Candidates not yet written
Section titled “Candidates not yet written”- Parallel agents + git worktrees
- Obsidian sync over Tailscale
- Clone-tab-at-remote-cwd (OSC 7 pipeline across SSH+Zellij)
See also: kernel patterns for universal structural patterns.