After reading this thread and a few other similar ones, I tried out BorgBackup and have been massively impressed with it’s efficiency.

Data that hasn’t changed, is stored under a different location, or otherwise is identical to what’s already stored in the backup repository (both in the backup currently being created and all historical backups) isn’t replicated. Only the information required to link that existing data to its doppelgangers is stored.

The original set of data I’ve got being backed up is around 270gb: I currently have 13 backups of it. Raw; thats 3.78tb of data. After just compression using zlib; that’s down to 1.56tb. But the incredible bit is after de-duplication (the part described in the above paragraph), the raw data stored on disk for all 13 of those backups: 67.9gb.

I can mount any one of those 13 backups to the filesystem, or just extract any of 3.78tb of files directly from that backup repository of just 67.9gb of data.

Linux?

I just use sshfs to mount ssh shares and move files between them like any other folder.

Same with samba shares (windows).

Configure ethernet with fixed IPs, and configure wifi to use your phone hotspot.

Then you can use one to troubleshoot the other as needed.

Then your normal setup would be wired between the pi+laptop, with the laptop connected to local wifi for internet.

True, the browser extension can be rather annoying. I tend to do any edits through either the android app, or the web page.

Interesting, that I was not aware of. I’ve never run into a scenario where I’ve had to add/edit while offline.

When using vaultwarden however, you can be offline as long as the client can still reach the server (ie they are within the same lan network or are the same machine). You’d still be fine to add/edit while your home wan is out for example, just not on the go.

Plus there’s the no-internet package mentioned in that link, but it’s limited to the desktop application.

Bitwarden is (primarily) a single db synced between devices via a server. A copy is kept locally on each device you sign into.

Changes made to an offline copy will sync to the server and your other devices once back online. (with the most recent change to each individual item being kept if there are multiple changes across several devices) /edit: the local copy is for access to your passwords offline. Edits must be made with a connection to the server your account resides on, be that bitwardens or your own.

If you host your own sync server via vaultwarden, you can easily maintain multiple databases (called vaults) either with multiple accounts, or with a single account and the organizations feature. (options for creating vaults separate from your main one and sharing those vaults with multiple accounts) You can do this with regular bitwarden as well, but have to pay for the privilege.

Using vaultwarden also gives you all the paid features of bitwarden for free (as it’s self-hosted instead of using public servers)

I’ve been incredibly happy with it after setting it up ~3 months ago. Worth looking into.

Jesus, you can run more than one piece of software on each bit of hardware…

Why spread out across 12-13 machines? Seems like a huge waste of power, and a whole bunch of extra to maintain.

It’s a reverse proxy infront of you’re services. That’s fundamental to how a RP functions. Just like your own reverse proxy.

Emby, Jellyfin, and Plex will all detect connection speed, adjust quality settings, and transcode the media to playback without buffering.

I wouldn’t recommend Plex. They’ve been steadily moving away from self-hosted private media servers and towards just serving comercial content to you.

I myself run Emby as I’m rather fond of their development team and their attitude towards privacy. It does require payment for ‘emby premier’, ie the installable client apps and transcoding features, but it has single payment lifetime licenses as well as monthly.

Jellyfin is a popular open source option that is built on a fork of Embys older open source code before they went closed source.

Either would work for you.

Tbh, laziness and lack of need.

I’ll probably reconsider once renewal comes around, but that’s ~4 years away. Until then, as long as things continue functioning: meh. Doesn’t really make a difference.

Idk, but it seems really stupid.

Having not actually looked into it at all:

I’m wondering if they have an api for updating records instead of traditional DDNS. Not the same thing AFAIK.

Either way, I’m already using cloudflare as a nameserver so this shouldn’t matter as much as I thought.

I’m an idiot.

I already do this. The swap to Squarespace wont actually effect me.

🤦

Oh fuck.

I just remembered I use cloudflare as my name servers, google (well, Squarespace now) only handles the registration.

I probably don’t have to do anything then.

Kinda feel like a moron now…

Are they supporting FOSS, or looking to buy out the project to make it a closed in-house solution and avoid the bad publicity they created this last week?

Ah; then host the OpenVPN server from hetzner, the pi as a client, then configure the server to route traffic out through the pi client into your LAN. Your own little vpn tunnel, instead of using something like cloudflare tunnels.

Wan client > Hetzner > pi client > lan service

OpenVPN host to keep mobile devices behind pihole and able to access non-public lan services.

I’ve run it on every pi I’ve used for several years now, though they are typically pretty quiet systems. Usually something like pihole or a reverse proxy. Not much writing going on. I’ve restored about a dozen of those images and never had an issue.

I also tend to keep 3-6 backups at a time. If the most recent is messed up for some reason, there’s others to try. (though I’ve never actually had to try more than one)

Then when the main PI returns it creates a conflict…

Don’t you then run into MAC conflicts?

How do you keep both on the network?

How do you manage automatically transferring the ip of the main rpi to the backup rpi when the first disappears?