build(deploy)!: Learn's database password is LEARN_POSTGRES_PASSWORD, as Train's and Todo's are prefixed
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>
This commit is contained in:
parent
3ac1880ac8
commit
5727a15353
1 changed files with 7 additions and 4 deletions
|
|
@ -99,8 +99,11 @@ COMPOSE_FILE=compose.learn.yaml
|
|||
|
||||
# The password of the instance's PostgreSQL superuser, halkyon_learn, which Learn's
|
||||
# server signs in as, and backups and deploys dump as (Train's and Todo's servers have
|
||||
# roles of their own). Generate: openssl rand -base64 32
|
||||
POSTGRES_PASSWORD=
|
||||
# roles of their own), as TRAIN_POSTGRES_PASSWORD and TODO_POSTGRES_PASSWORD are their
|
||||
# roles' (named POSTGRES_PASSWORD until 2 Nov 2026). Set once, when the database is
|
||||
# made: PostgreSQL keeps the password it was made with, whatever this says later.
|
||||
# Generate: openssl rand -base64 32
|
||||
LEARN_POSTGRES_PASSWORD=
|
||||
|
||||
# Learn's pepper for hashing session keys (server-side sessions), as Train's and Todo's
|
||||
# are TRAIN_ and TODO_SESSION_KEY_HASH_PEPPER (named SESSION_KEY_HASH_PEPPER until
|
||||
|
|
|
|||
Loading…
Reference in a new issue