From 536652b5b6928847b3bc8938168ffc7b9832b373 Mon Sep 17 00:00:00 2001 From: Quartz Syncer Date: Wed, 21 Jan 2026 22:48:48 -0700 Subject: [PATCH] Published multiple files --- .../13 TECH SETUP/13.12 PROCESSES/Backups.md | 10 ++++++---- .../22 SELF HOSTING/22.12 SERVICES/GoToSocial.md | 8 ++++++++ 2 files changed, 14 insertions(+), 4 deletions(-) create mode 100644 content/20-29 HOBBYS/22 SELF HOSTING/22.12 SERVICES/GoToSocial.md diff --git a/content/10-19 LIFE/13 TECH SETUP/13.12 PROCESSES/Backups.md b/content/10-19 LIFE/13 TECH SETUP/13.12 PROCESSES/Backups.md index b30438a..41d1ebd 100644 --- a/content/10-19 LIFE/13 TECH SETUP/13.12 PROCESSES/Backups.md +++ b/content/10-19 LIFE/13 TECH SETUP/13.12 PROCESSES/Backups.md @@ -2,13 +2,13 @@ publish: true title: Backups created: 2026-01-20T13:21:41.646-07:00 -modified: 2026-01-20T13:30:33.530-07:00 +modified: 2026-01-21T22:48:12.310-07:00 cssclasses: "" --- ## Local For me local backups happen in two main ways -1. Backups to a VPS using [[Syncthing]] +1. Backups to a VPS using [[20-29 HOBBYS/22 SELF HOSTING/22.12 SERVICES/Syncthing]] 2. Backups to a USB stick that lives in my emergency kit ### USB Backups For USB backups I had a few key requirements @@ -16,7 +16,7 @@ For USB backups I had a few key requirements 2. Decryption should be able to take place on any Windows, Mac, or Linux device 3. Decryption must be simple enough that an intermediate user should be able to manage it given instructions (this is in case someone needs this data if I am no longer around to impart my wisdom) -Given these requirements I settled on using [[VeraCrypt]] to create an encrypted container formatted with exFat on a USB drive. This way someone can install the software and, given my key, decrypt the data. +Given these requirements I settled on using [[10-19 LIFE/13 TECH SETUP/13.11 APPS/VeraCrypt]] to create an encrypted container formatted with exFat on a USB drive. This way someone can install the software and, given my key, decrypt the data. I created the following helper functions to make this processes a little less cumbersome for myself on a monthly basis. #### Mount/Unmount Container @@ -86,4 +86,6 @@ vault-sync() { rsync -av --delete "$source/" "$mount_point/" echo "Sync complete" } -``` \ No newline at end of file +``` +## Cloud +For services on my VPS's I backup docker volumes using [docker-volume-backup](https://github.com/offen/docker-volume-backup) \ No newline at end of file diff --git a/content/20-29 HOBBYS/22 SELF HOSTING/22.12 SERVICES/GoToSocial.md b/content/20-29 HOBBYS/22 SELF HOSTING/22.12 SERVICES/GoToSocial.md new file mode 100644 index 0000000..29e19da --- /dev/null +++ b/content/20-29 HOBBYS/22 SELF HOSTING/22.12 SERVICES/GoToSocial.md @@ -0,0 +1,8 @@ +--- +publish: true +created: 2026-01-21T22:20:37.846-07:00 +modified: 2026-01-21T22:26:52.945-07:00 +cssclasses: "" +--- + +I host [GoToSocial](https://gotosocial.org/) on a VPS. It is my primary [Fediverse](https://en.wikipedia.org/wiki/Fediverse) interface and it has been more than adequate for my needs. The only thing I do that is of much difference to the standard deployment is that I back up the docker volume using my standard [[10-19 LIFE/13 TECH SETUP/13.12 PROCESSES/Backups\|backup]] process for cloud services. \ No newline at end of file