From 2de7bb68abefd505bca532fdd797f4ddcbb20746 Mon Sep 17 00:00:00 2001 From: tiennm99 Date: Wed, 16 Sep 2026 15:06:01 +0700 Subject: [PATCH] docs: record compose.yml naming convention for new services New services take the current Compose spec filename. Existing docker-compose.yml files stay as they are so unrelated changes do not carry a rename. --- CLAUDE.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 0b783a4..4dff3bf 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -4,6 +4,13 @@ Personal docker compose collection. One directory per service, each holding `compose.yml`, its own `README.md`, a committed `.env.example`, and a gitignored `.env`. +## File naming + +New services use `compose.yml` — the current Compose spec name, and the +shorter one. Existing services that still use `docker-compose.yml` stay as +they are; do not rename them, not even while touching the file for something +else. + The root `README.md` is an index only — it covers the shared conventions and links out to each service. Per-service detail (variables, ports, storage) belongs in that service's README, not the root one. Adding a service means