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,7 +1,7 @@
|
|||
# Dictionary files
|
||||
|
||||
For an instance that supplies its dictionary files itself, rather than the
|
||||
`dictionaries` service keeping them current (`compose.yaml`): put the files
|
||||
`dictionaries` service keeping them current (`compose.learn.yaml`): put the files
|
||||
(`*.jsonl`, `*.jsonl.gz`, made by `halkyon_learn_curator`) here and mount this
|
||||
folder into the server as the comment there says. Mind EDRDG's licence: a server
|
||||
showing its dictionaries must update them at least once a month. Not kept in git.
|
||||
|
|
|
|||
Loading…
Reference in a new issue