The link carried the deploy that switched the server's COMPOSE_FILE over (2 Nov 2026).
BREAKING CHANGE: an instance whose deploy/.env still names compose.yaml, or sets no
COMPOSE_FILE, must name compose.learn.yaml first.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
Still the password of the instance's PostgreSQL superuser, halkyon_learn, which Learn's
server signs in as; only its name in deploy/.env changes. PostgreSQL's image still takes
it as POSTGRES_PASSWORD, its own variable.
BREAKING CHANGE: an instance's deploy/.env names it LEARN_POSTGRES_PASSWORD.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
No file has Compose's default name any more, so .env's COMPOSE_FILE is always set,
naming compose.learn.yaml first (.env.example sets it). compose.yaml stays as a link to
compose.learn.yaml for the one deploy that switches learn.halkyon.eu's .env over: the
deploy's merge runs with the COMPOSE_FILE from before. A later commit removes it.
BREAKING CHANGE: an instance's deploy/.env must set COMPOSE_FILE, starting with
compose.learn.yaml, before the link goes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
