From ec3ab6a25fbdacb8d092997a45f5b5f14e8715d3 Mon Sep 17 00:00:00 2001 From: ogrechko Date: Wed, 9 Sep 2026 06:20:52 +0000 Subject: [PATCH] Pin explicit Compose project name MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Without this, Compose derives the project name from the directory basename — fine today, but a silent trap if this repo is ever checked out under a differently-named sibling path/host and someone reuses "top-tickets" elsewhere. Value matches the current derived name exactly, so this is a no-op for the running deployment. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01Gh2UXUQUVBWroWEnn1FLFG --- docker-compose.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docker-compose.yml b/docker-compose.yml index 4ff1d2a..156dd03 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -1,3 +1,8 @@ +# Explicit project name — without this, Compose derives it from the +# directory basename, which can collide with an unrelated sibling repo +# checked out under the same name on another host/path. Never omit this. +name: top-tickets + services: app: build: .