build(deploy)!: the instance's compose file is compose.learn.yaml, beside compose.train.yaml and compose.todo.yaml
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>
This commit is contained in:
parent
5469ce791f
commit
3ac1880ac8
1 changed files with 267 additions and 260 deletions
|
|
@ -1,6 +1,6 @@
|
|||
# The instance's assistants (Halkyon Learn's ADR 0021, points 4 and 8, D37, D38, D63):
|
||||
# copy to deploy/assistants.env, restrict it (chmod 600), and fill in. It is git-ignored,
|
||||
# goes to Halkyon Learn's server alone (compose.yaml, `env_file`), never into an image,
|
||||
# goes to Halkyon Learn's server alone (compose.learn.yaml, `env_file`), never into an image,
|
||||
# the database or its backups; keep it with deploy/.env's secrets (in Proton Pass).
|
||||
# Without the file, the instance offers no assistant, as before. A change takes a
|
||||
# restart: docker compose up -d server. Anything the server can't use stops it as it
|
||||
|
|
|
|||
Loading…
Reference in a new issue