Pin explicit Compose project name

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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gh2UXUQUVBWroWEnn1FLFG
This commit is contained in:
ogrechkoandClaude Sonnet 5 committed 2026-09-09 06:20:52 +00:00
1 parent e42fd4697f
commit ec3ab6a25f
1 file changed
+5
+5
View File
@@ -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: services:
app: app:
build: . build: .