chore(macmini): pin COMPOSE_PROJECT_NAME=manacore-monorepo

The Mac Mini's existing containers were originally created under the
project name `manacore-monorepo` (from the historical directory name)
but the current checkout lives in `mana-monorepo`. Without an explicit
pin, every `docker compose up` from this directory spawned a SECOND
project, creating duplicate containers and silent volume conflicts.
The 2026-04-07 outage recovery had to pass `-p manacore-monorepo`
manually for exactly this reason.

Pinning the name in `.env.macmini.example` (which is checked in)
means any fresh checkout that copies it to `.env.macmini` inherits
the right project name automatically. The pin is also live on the
production Mac Mini in `.env` and `.env.macmini` (untracked).

Removing this line WILL break the next deployment — the comment
in the file says so explicitly.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Till JS 2026-04-07 22:31:25 +02:00
parent 171fbd18be
commit a94abd37e0

View file

@ -1,6 +1,18 @@
# Mac Mini Production Environment
# Copy to .env.macmini and fill in the values
# ============================================
# Compose project name (pinned, do not change)
# ============================================
# All Mac Mini containers were originally created under this project
# name, which mismatches the current directory name (mana-monorepo).
# Pinning the project name here means anyone running 'docker compose ...'
# from the repo root automatically lands in the same project as the
# already-running containers, instead of silently spawning a duplicate
# project with the same compose file. Removing this line WILL break
# the next deployment.
COMPOSE_PROJECT_NAME=manacore-monorepo
# ============================================
# Database (PostgreSQL)
# ============================================