atom/town
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update readme.md

Browse Source
This commit is contained in:
futile
2026-07-18 21:54:38 +01:00
parent ae19469f2a
commit 973f5a7d12
1 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+12 -1
View File
@@ -80,6 +80,8 @@ specifics for everything
backups are done with [vykar](https://vykar.borgbase.com) to [borgbase](https://borgbase.com) 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** **creating**
- if on a new borgbase repo, run `vykar init` first - 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/`) - 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** **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 ## todo
- further secure the server (ratelimiting, hardening...) - further secure the server (ratelimiting, hardening...)