diff options
| -rw-r--r-- | Installation-Guide.md | 24 |
1 files changed, 6 insertions, 18 deletions
diff --git a/Installation-Guide.md b/Installation-Guide.md index 00817cc..c932eaf 100644 --- a/Installation-Guide.md +++ b/Installation-Guide.md @@ -446,31 +446,19 @@ To run [`.docker/app/backup.sh`](https://github.com/tt-rss/tt-rss/blob/main/.doc `docker compose exec backups /etc/periodic/weekly/backup` -Alternatively, if you want to initiate backups from the host you can do something like this: +Alternatively, if you want to initiate backups from the host (or if you're using PostgreSQL 18+, currently incompatible with the `backup` container) you can do something like this: ```sh source .env -docker compose exec db /bin/bash \ +docker compose exec \ + -e PGPASSWORD="$TTRSS_DB_PASS" \ + db \ + /bin/bash \ -c "export PGPASSWORD=$TTRSS_DB_PASS \ - && pg_dump -U $TTRSS_DB_USER $TTRSS_DB_NAME" \ + && pg_dump -U $TTRSS_DB_USER $TTRSS_DB_NAME" \ | gzip -9 > backup.sql.gz ``` -The `backup` container uses the PostgreSQL 17 client, and isn't currently compatible with PostgreSQL 18+. -Something like this following could be ran (from your Docker Compose directory or with `COMPOSE_PROJECT_NAME` defined properly) to back up a PostgreSQL 18 DB: - -```sh -source .env -docker run --rm \ - --network "${COMPOSE_PROJECT_NAME:-$(basename "$PWD")}_default" \ - -e PGPASSWORD="$TTRSS_DB_PASS" \ - postgres:18-alpine pg_dump \ - -h "${TTRSS_DB_HOST:-db}" \ - -U "$TTRSS_DB_USER" \ - "$TTRSS_DB_NAME" | gzip > backup.sql.gz - -``` - #### Restoring backups The process to restore the database from a `backups` container backup might look like this: |