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
|
|
@ -25,7 +25,7 @@ webServer:
|
|||
publicPort: 443
|
||||
publicScheme: https
|
||||
|
||||
# The database: the `postgres` service of deploy/compose.yaml, reachable only inside
|
||||
# The database: the `postgres` service of deploy/compose.learn.yaml, reachable only inside
|
||||
# the Compose network (it publishes no port), so no TLS between server and database.
|
||||
# The password comes from the environment (SERVERPOD_DATABASE_PASSWORD, set in
|
||||
# deploy/.env); there is no production passwords.yaml.
|
||||
|
|
|
|||
Loading…
Reference in a new issue