From 86c88b156df2cb8cf2e02d31ece01c1f63f511d1 Mon Sep 17 00:00:00 2001 From: fox Date: Wed, 30 Sep 2020 10:14:28 +0000 Subject: [PATCH] Update page 'Home' --- Home.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/Home.md b/Home.md index bec012d..ded2dcc 100644 --- a/Home.md +++ b/Home.md @@ -94,17 +94,17 @@ You will need to set ``SELF_URL_PATH`` to a correct (i.e. visible from the outsi Unless you have `backups` container disabled, stock configuration makes automatic tt-rss database backups once a week to a separate storage volume. -A process to restore from such backup would look similar to this: +A process to restore from such backup would look like this: + +1. Enter backups container shell: `docker-compose exec backups /bin/sh` +2. Inside the container, find latest backup: `ls -t /backups/*.sql.gz` +3. Restore the backup: ```sh -$ docker-compose exec backups /bin/sh -/ # ls /backups -ttrss-backup-20200930.sql.gz -... -/ # zcat /backups/ttrss-backup-20200930.sql.gz | psql -h db -U $DB_USER $DB_NAME +# zcat /backups/ttrss-backup-yyyymmdd.sql.gz | psql -h db -U $DB_USER $DB_NAME ``` -Alternatively, you can use something like this: +Alternatively, if you want to initiate backups from the host, you can use something like this: ```sh source .env