

I’ve only done my “is it even possible” research so far, but these look promising:
https://medium.com/@amandubey_6607/docker-registry-caching-a2dfefecfff5
I’ve only done my “is it even possible” research so far, but these look promising:
https://medium.com/@amandubey_6607/docker-registry-caching-a2dfefecfff5
Huh. I was just considering establishing a caching registry for other reasons. Ferb, I know what we’re going to do today!
Use plz
and add a Makefile? :)
plz make sandwich
This is why I can’t/don’t have a lot of the “best practices” in my family archive. I’m not encrypting local drives, I’m not using BTRFS, or a ZFS pool. If I did I’d have to ensure my Will provided for the lawyer to hire a tech shop to help recover them. No, exFAT and NTFS, in the clear so those left behind can just plug them in and get to making their own copies. Otherwise the archive would die with me.
Does that mean someone could steal my drives and go through my family photos? Sure. I hope it brings them much guilt, something a garbled encrypted drive could never do.
exFAT is a newer and viable alternative to FAT32, with better size limits and some pretty good cross-platform capabilities. That said, if your primary access is through Windows, NTFS may have some better features and is at least read-only on other platforms.
Gitea and therefore Forgejo also have container registry functionality, I use that for private builds.