From 973f5a7d12ebc8c5a44de50658bdbe501d2090a7 Mon Sep 17 00:00:00 2001 From: futile Date: Sat, 18 Jul 2026 21:54:38 +0100 Subject: [PATCH] update readme.md --- README.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 6c683ea..4716ed6 100644 --- a/README.md +++ b/README.md @@ -80,6 +80,8 @@ specifics for everything backups are done with [vykar](https://vykar.borgbase.com) to [borgbase](https://borgbase.com) +always remember to `docker compose stop` before doing any of this! + **creating** - if on a new borgbase repo, run `vykar init` first - to back up, run `sudo vykar backup` (sudo required as we are accessing `/var/lib/docker/volumes/`) @@ -90,7 +92,16 @@ backups are done with [vykar](https://vykar.borgbase.com) to [borgbase](https:// ``` **restoring** -- to restore the backup, run `vykar list` to find a snapshot to use, then `sudo vykar restore abcd1234 /var/lib/docker/volumes/` +the restore process is kind of fucked up but doable + +- restore on new system + - run `vykar list` to find a snapshot to use + - `sudo rm -rf /var/lib/docker/volumes/` + - then `sudo vykar restore abcd1234 /var/lib/docker/volumes/` + - figure out the UID:GID for all containers and `sudo chown -R UID:GID /var/lib/docker/volumes/.../_data/` their respective volumes +- restore on same system + - run `vykar list` to find a snapshot to use + - then `sudo vykar restore abcd1234 /var/lib/docker/volumes/` ## todo - further secure the server (ratelimiting, hardening...)