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
|
|
@ -2,7 +2,7 @@
|
|||
# people watch and listen to learn from (Halkyon Learn's Watch screen), suggested to them
|
||||
# by the instance. Switched on in .env, with the domain it answers at:
|
||||
#
|
||||
# COMPOSE_FILE=compose.yaml:compose.jellyfin.yaml
|
||||
# COMPOSE_FILE=compose.learn.yaml:compose.jellyfin.yaml
|
||||
# JELLYFIN_DOMAIN=jellyfin.example.org
|
||||
#
|
||||
# Its files are the server's, in ./jellyfin (config, cache, media), owned by a user ID
|
||||
|
|
|
|||
Loading…
Reference in a new issue