Eager Eagle

fwiw, I used Kopia for around a year, but eventually the backup got corrupted with a BLOB not found error and there was no way to fix it.

similar to this issue, except that nothing would fix or improve the situation https://github.com/kopia/kopia/issues/1087

and because it seemed to be an issue with the repo (not just with a snapshot), the remote copy was also borked. I couldn’t even list the snapshots.

I’ve since migrated to Rustic (though Restic might be more reliable today).

This seems to be the a similar issue too, but I was nowhere near the scale of this user. There are other similar reports that may or may not be linked to the same root cause, so it’s hard to say how rare this problem is.

deleted by creator

Isn’t that creating hardlinks between source and dest? Hard links only work on the same drive. And I’m not sure how that gives you “time travel”, as in, browsing snapshots or file states at the different times you ran rsync.

Edit: ah the hard link is between dest and the link-dest argument, makes more sense.

I wouldn’t bundle fs and backup compression in the same bucket, because they have vastly different reqs. Backup compression doesn’t need to be optimized for fast decompression.

yeah, more often than not I notice the bottleneck being the storage drive itself, not rsync.

yeah, it doesn’t, it’s just for file transfer. It’s only useful if transferring files somewhere else counts as a backup for you.

To me, the file transfer is just a small component of a backup tool.

It works fine if all you need is transfer, my issue with it it’s just not efficient. If you want a “time travel” feature, your only option is to duplicate data. Differential backups, compression, and encryption for off-site ones is where other tools shine.

I tried portainer for a while, but it was almost useless to me, as I’d always end up in the command line anyway. So I dropped that and any other dashboard idea.

Yeah, I have everything as compose.yaml stacks and those stacks + their config files are in a git repo.

it might be worth watching this PR for memos, which adds encryption at rest. I can’t vouch for it, as I didn’t read the code but I do use memos and might consider this if it’s merged.

https://github.com/usememos/memos/pull/5130

This is not E2EE, but I don’t think E2EE is that important if you’re hosting your own data. And clients can use TLS for encryption in transit.

Great, I wish there was a way to disable airbags too. I wear glasses and the having the frame marked on my face in a car crash always worries me.

I also have no idea if my place has PVC or galvanized steel plumbing; or its designed electrical load. Why should users care about the DBMS.

I prefer being in formed

I change them all to bind mounts. Managed volumes is where data goes to die, if it’s not in my file tree I’ll forget it.

Because that’s a release page. The first paragraph in the readme tells you what open webui is.

https://github.com/open-webui/open-webui

trees are great, this algae tank is just likely more efficient at producing oxygen

https://github.com/TimefoldAI/timefold-solver

I’ve been doing that for years. Rollbacks are very rare, to the point that it doesn’t make much of a difference whether I do them all at once or not, other than spending more time to do it.

If I wasn’t using containers for everything, sure. Otherwise it’s a bit of an excessive concern.

exactly my point, I’d suggest automating that before I bothered with PRs that upgrade versions, as it’s a waste of time.

“manual changes”, which connotes “local changes”

It doesn’t. Manual as in a PR with upgrades that you’re suggesting yourself, as opposed to running dependabot.

Putting up a PR with changes isn’t considered a manual anything.

If I have to open a PR myself, that’s very much a manual change.