aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJulien Dessaux2023-12-24 22:37:59 +0100
committerJulien Dessaux2023-12-24 22:37:59 +0100
commitbbd57a747348727cb8fbb4bbbe6b530d03707ec7 (patch)
tree2713371e27650d3a264a95c39aad190f78fa9057
parentSmall fixes (diff)
downloadwww-bbd57a747348727cb8fbb4bbbe6b530d03707ec7.tar.gz
www-bbd57a747348727cb8fbb4bbbe6b530d03707ec7.tar.bz2
www-bbd57a747348727cb8fbb4bbbe6b530d03707ec7.zip
Updated miniflux's docs
-rw-r--r--content/blog/nix/migrating-vaultwarden.md4
-rw-r--r--content/docs/adyxax.org/miniflux/_index.md8
-rw-r--r--content/docs/adyxax.org/miniflux/backups.md38
3 files changed, 44 insertions, 6 deletions
diff --git a/content/blog/nix/migrating-vaultwarden.md b/content/blog/nix/migrating-vaultwarden.md
index a095070..1a960c0 100644
--- a/content/blog/nix/migrating-vaultwarden.md
+++ b/content/blog/nix/migrating-vaultwarden.md
@@ -189,11 +189,11 @@ mv srv/vaultwarden /srv/
export BORG_RSH="ssh -i /etc/borg-vaultwarden-db.key"
borg list ssh://borg@gcp.adyxax.org/srv/borg/vaultwarden-db
borg extract ssh://borg@gcp.adyxax.org/srv/borg/vaultwarden-db::dalinar-vaultwarden-db-2023-11-19T00:00:01
+psql -h localhost -U postgres -d vaultwarden
```
Restoring the data itself is done with the psql shell:
-```sh
-psql -h localhost -U postgres -d vaultwarden
+```sql
ALTER USER vaultwarden WITH PASSWORD 'XXXXX';
\i tmp/vaultwarden.sql
```
diff --git a/content/docs/adyxax.org/miniflux/_index.md b/content/docs/adyxax.org/miniflux/_index.md
index e71c3c1..43b8a11 100644
--- a/content/docs/adyxax.org/miniflux/_index.md
+++ b/content/docs/adyxax.org/miniflux/_index.md
@@ -5,10 +5,14 @@ description: miniflux.adyxax.org rss feed reader
## Introduction
-miniflux.adyxax.org is a [miniflux](https://miniflux.app/) instance that I have been using for about 5 years. It is a rss feed reader and aggregator written as a golang web application. It is a reliable piece of software and I never encountered any issue with it.
+miniflux.adyxax.org is a [miniflux](https://miniflux.app/) instance that I have been using for years. It is a rss feed reader and aggregator written as a golang web application. It is a reliable piece of software and I never encountered any issue with it.
## Captain's log
-- 2021-10-05 : migrated this instance to k3s on myth.adyxax.org
+- 2023-11-20 : migrated to nixos on myth.adyxax.org
+- 2023-10-26 : migrated to nixos on dalinar.adyxax.org
+- 2021-10-05 : migrated to k3s on myth.adyxax.org
+- circa 2018 : migrated to miniflux v2
+- circa 2016 : initial setup of miniflux v1
## Docs
diff --git a/content/docs/adyxax.org/miniflux/backups.md b/content/docs/adyxax.org/miniflux/backups.md
index 25d611d..79b66f3 100644
--- a/content/docs/adyxax.org/miniflux/backups.md
+++ b/content/docs/adyxax.org/miniflux/backups.md
@@ -5,7 +5,41 @@ description: Backups of miniflux.adyxax.org
## Documentation
-Backups are configured with borg on `myth.adyxax.org` to `yen.adyxax.org`.
+Backups are configured with borg on `myth.adyxax.org` and end up on `gcp.adyxax.org`.
-There is only on jobs :
+There is only one jobs :
- a pg_dump of miniflux's postgresql database
+
+## How to restore
+
+The first step is to deploy miniflux to the destination server, then I need to login with ssh and manually restore the data.
+```sh
+make run host=myth.adyxax.org
+```
+
+The container will be failing because no password is set on the database user yet, so stop it:
+```sh
+systemctl stop podman-miniflux
+```
+
+There is only one backup job for miniflux. It contains a dump of the database:
+```sh
+export BORG_RSH="ssh -i /etc/borg-miniflux-db.key"
+borg list ssh://borg@gcp.adyxax.org/srv/borg/miniflux-db
+borg extract ssh://borg@gcp.adyxax.org/srv/borg/miniflux-db::dalinar-miniflux-db-2023-11-20T00:00:01
+psql -h localhost -U postgres -d miniflux
+```
+
+Restoring the data itself is done with the psql shell:
+```sql
+ALTER USER miniflux WITH PASSWORD 'XXXXXX';
+\i tmp/miniflux.sql
+```
+
+Afterwards clean up the database dump and restart miniflux:
+```sh
+rm -rf tmp/
+systemctl start podman-miniflux
+```
+
+To wrap this up, migrate the DNS records to the new host and update the monitoring system.