Yeah, it needs those rules for e.g. port-forwarding into the containers.
But it doesnt really ‘nuke’ existing ones.
I have simply placed my rules at higher priority than normal. Very simple in nftables and good to not have rules mixed between nftables and iptables in unexpected ways.
You should filter as early as possible anyways to reduce ressource usage on e.g. connection tracking.
BTRFS or ZFS and then you can just rollback to an earlier snapshot.
So i understood you just want some local storage system with some fault tolerance.
ZFS will do that. Nothing fancy, just volumes as either blockdevice or ZFS filesystem.
If you want something more fancy, maybe even distributed, check out storage cluster systems with erasure coding, less storage wasted than with pure replication, though comes at reconstruction cost if something goes wrong.
MinIO comes to mind, tough i never used it… my requirements seem to be so rare, these tools only get close :/
afaik you can add more disks and nodes more or less dynamically with it.
The interface is weird and unintuitive at times…
I have a dropdown menu at the button “New custom field” and can select “Hidden”.
I like that KeePass has the option to set fields as protected
Vaultwarden can do that, though its quite stiff in some aspects like folders… subfolders? nonexistant…
Ideally keypass would allow handling such conflicts internally.
Thats the big disadvantage of a single-file approach.
Could easily be avoided e.g. sync whole folder and now you can have multiple files, e.g. 1 write file per program used.
big reason why i switched to kopia, borg just doesnt cut it anymore…