I’ve found the following setup works well. It’s simpler, but less featureful:
Website is a git repo stored on a nas, and backed up. (GitHub would also work; private repos were scarce when I set this up). It’s published with “s3 sync”, and sits behind a cheap cdn.
Desktop is backed up to NAS (via NFS; would use syncthing if I was setting this up again. Previously, I used Unison, which confused some other users of the desktop, but I like it anyway.)
NAS uses synology’s client side encrypted HyperBackup to B2.
Calendar and contacts are on the nas, using baikal, which runs in a docker image on the synology. My phone is fine with periodic access to the contacts and calendar server, so this sits behind the firewall, and is not accessible via the internet.
Total monthly cost is pennies, not counting domain names, or the B2 backup data.
The main problem is that all the data will be compromised if the NAS is stolen. I’m looking for a good solution to that next.
Website is a git repo stored on a nas, and backed up. (GitHub would also work; private repos were scarce when I set this up). It’s published with “s3 sync”, and sits behind a cheap cdn.
Desktop is backed up to NAS (via NFS; would use syncthing if I was setting this up again. Previously, I used Unison, which confused some other users of the desktop, but I like it anyway.)
NAS uses synology’s client side encrypted HyperBackup to B2.
Calendar and contacts are on the nas, using baikal, which runs in a docker image on the synology. My phone is fine with periodic access to the contacts and calendar server, so this sits behind the firewall, and is not accessible via the internet.
Total monthly cost is pennies, not counting domain names, or the B2 backup data.
The main problem is that all the data will be compromised if the NAS is stolen. I’m looking for a good solution to that next.