7a2e0e044c
The db service dumped the DB on backup (pg_dump pre-hook) but shipped no restore hook, and a file-level restore does not reload into the running postgres, so a restored backup silently kept the live (un-restored) state. Add pg_backup.sh (backup=pg_dump|gzip into the postgresql_data volume; restore=terminate conns + DROP DATABASE WITH FORCE + createdb + reimport), mount it via a config, and wire the backupbot backup/restore hooks. Same fix as the immich / mattermost-lts / ghost recipes.
23 lines
524 B
Plaintext
23 lines
524 B
Plaintext
TYPE=discourse
|
|
|
|
DOMAIN=discourse.example.com
|
|
## Domain aliases
|
|
#EXTRA_DOMAINS=', `www.discourse.example.com`'
|
|
LETS_ENCRYPT_ENV=production
|
|
|
|
# Outgoing email
|
|
#DISCOURSE_SMTP_HOST=
|
|
#DISCOURSE_SMTP_PORT=
|
|
#DISCOURSE_SMTP_USER=
|
|
#DISCOURSE_SMTP_PROTOCOL=
|
|
#DISCOURSE_SMTP_AUTH=
|
|
# Set this if you send e-mails from a different domain than noreply@$DOMAIN
|
|
#DISCOURSE_NOTIFICATION_EMAIL=$SMTP_USER
|
|
|
|
# SMTP authentication
|
|
#COMPOSE_FILE="compose.yml:compose.smtpauth.yml"
|
|
#SECRET_SMTP_PASSWORD_VERSION=v1
|
|
|
|
SECRET_DB_PASSWORD_VERSION=v1
|
|
|