Repository navigation
Home
Serge Gatezh edited this page Oct 8, 2026
·
4 revisions
Development container and standalone Docker images published to ghcr.io/gatezh/devcontainers/.
New here? Start with Choosing an Image, then read that image's README in the repo for the details.
| Page | What it answers |
|---|---|
| Choosing an Image | Which of the six images do I want? |
| Image Tags and Rebuild Policy | What does latest mean, when does it move, and what should I pin? |
| Cloudflare CLI | Which images run cf, when to move a project off Wrangler, credentials in a container |
| Troubleshooting | Symptoms that span more than one image |
| Docker Disk Maintenance | Docker is eating the disk — what do I run? |
| Page | What it answers |
|---|---|
| Branch Protection and Renovate Auto-Merge | How the CI complete gate and auto-merge are configured |
| Incident: Docker Disk Exhaustion (2026-09-07) | Why Docker filled the disk and what actually fixed it |
If a document goes stale when this repo's code changes, it belongs in the repo. If it goes stale when an external system changes — Docker Desktop, GitHub settings, an upstream tool — or it spans several images, it belongs here.
That rule is what keeps the two surfaces from drifting:
| In the repo | Why there |
|---|---|
Per-image README.md
|
A tag list or tool table must change in the same commit as the Dockerfile it describes. Splitting them guarantees drift. |
.claude/CLAUDE.md, .claude/rules/*
|
Conventions enforced against the code in review. |
.github/workflows/README.md |
Describes the workflows sitting next to it. |
docs/plans/, docs/superpowers/
|
Planning and design artifacts tied to specific changes. |
| In the wiki | Why here |
|---|---|
| Cross-image guides | Belong to no single image, so no README is the right home. |
| Host / Docker Desktop procedures | Go stale when Docker changes, not when this repo does. |
| GitHub settings runbooks | Describe configuration that lives in repo settings and cannot be reviewed in a PR. |
| Incident writeups | Operational history, not code. |
Nothing is duplicated. Wiki pages link to READMEs; READMEs link back here. If you find the same fact in both places, one of them is wrong — fix the repo copy and make the wiki link to it.
- Every page ends with a Sources section citing the PRs and issues the knowledge came from, plus a Last verified date. Wiki pages rot silently; the date is the signal.
- Pages are procedures and reference material — exact labels, runnable commands. Background belongs in a linked incident writeup, not inline.
- The wiki has no review and no CI. Anything that can be checked by CI belongs in the repo instead.
- #123 — added the Docker disk runbook and cheatsheet that this wiki was reorganized around
- #132 — per-image README drift, tracked separately
Last verified: 2026-09-09