Try goharbor.io, that's what I use. I think (but I'm not sure) that Forgejo/Gitea and Gitlab can also cache images.
DasFaultier
Blonde for me plz
"Effi Briest" all the way.
I have limited Python experience, but I always thought that's what virtualenvs and requirements.txt files are for? When I used those, I found it easy enough to use.
Cloud-init. The config yaml is rather straight forward, but I can't convince my VM to execute it, and it's driving me nuts.
If my wife didn't have an abortion, she would be fucking dead by now, so how would that even be a consideration that a sane person would make? Does an abortion make a woman less of a person? No. But does it make her less loveable? Also no. But is it a red flag that she had sex before, maybe even with a different person? No, and fuck patriarchy.
Nope nopedi nope.
Good to hear! When you go with the National Archives UK, you can't fail. They have some very, VERY competent people in staff over there, who are also quite active in the DigiPres community. They are also the inventors of DROID and the maintainers of the widely used PRONOM database of file formats. https://www.nationalarchives.gov.uk/PRONOM/Default.aspx Absolute heroes of Digital Preservation.
Yeah, you can always go crazy with (off site) copies. There's a DigiPres software system literally called LOCKSS (Lots Of Copies Keep Stuff Safe).
The German Federal Office for Information Security recommends a distance of at least 200km between (professional) sites that keep georedundant copies of the same data/service, so depending on your upload capacity and your familiarity with encryption (ALWAYS backup your keys!), some cloud storage provider might even be a viable option to create a second site.
Spare drives do absolutely work as well, but remember that, depending on the distance, data there will get more or less outdated and you might not remember to refresh the hardware in a timely manner.
A safe deposit box is something that I hadn't considered for my personal preservation needs yet, but sounds like a good idea as well.
Whatever you use, also remember to read back data from all copies regularly and recalculate checksums for fixity checks to make sure your data doesn't get corrupted over time. Physical objects (like books) decay slowly over time, digital objects break more spontaneously and often catastrophically.
This is my day job, so I'd like to weigh in.
First of all, there's a whole community of GLAM institutions involved in what is called Digital Preservation (try googling that specifically). Here in Germany, a lot of them have founded the Nestor Group (www.langzeitarchivierung.de) to further the case and share knowledge. Recently, Nestor had a discussion group on Personal Digital Archiving, addressing just your use case. They have set up a website at https://meindigitalesarchiv.de/ with the results. Nestor publishes mostly in German, but online translators are a thing, so I think you will be fine.
Some things that I want to address from your original post:
- Keep in mind that file formats, just like hardware and software, become obsolete over time. Think about a migration strategy for your files to a more recent format of your current format falls out of style and isn't as widely supported anymore. I assume your photos are JPGs, which are widely not considered safe for preservation, as they decay with subsequent encoding runs and use lossy compression. A suitable replacement might be PNG, though I wouldn't go ahead and convert my JPGs right away. For born digital photo material, uncompressed TIFF is the preferred format.
- Compression in general is considered a risk, because a damaged bit will potentially impact a larger block of compressed data. Saving a few bytes on your storage isn't worth listing your precious memories.
- Storage media have different retention times. It's true that magnetic tape storage has the best chances for survival, and it's what we use for long term cold storage, but it's prohibitively expensive for home use. Also, it's VERY slow on random access, because tape has to be rewound to the specific location of your file before reading. If you insist on using it, format your tapes using LTFS to eliminate the need for a storage management system like IBM Spectrum Protect. The next best choice of storage media are NAS grade HDDs, which will last you upwards of five years. Using redundancy and a self correcting file system like ZFS (compression & dedup OFF!) will increase your chances of survival. Keep you hands off optical storage media; they tend to decay after a year already according top studies on the subject. Flash storage isn't much greater either, avoid thumb drives at all cost. Quality SSD storage might last you a little longer. If you use ZFS or a comparable file system that provides snapshots, you can use that to implement immutability.
- Kudos for using Linux standard tooling; it will help other people understand your stack of anything happens to you. Digital Preservation is all about removing dependencies on specific formats, technologies and (importantly) people.
- Backup is not Digital Preservation, though I will admit that these two tend get mixed into one another in personal contexts. Backups save the state of a system at a specific point in time, DigiPres tries to preserve only data that isn't specific to a system and tends to change very little. Also, and that is important, DigiPres tries to save context along with the actual payload, so you might want to at least save some metadata along with your photos and store them all in a structure that is made for preservation. I recommend BagIt; there's a lot of existing tooling for creating it, it's self-contained, secured by strong checksums and it's an RFC.
- Keep complexity as low as possible!
- Last of all, good on you for doing SOMETHING. You don't have to be perfect to improve your posture, and you're on the right track, asking the right questions. Keep on going, you're doing great.
Come back at me if you have any further questions.
Gitlab at work, because, well, it's there and it works just fine.
Forgejo at home, because it's far less resource hungry.
In the end Git is a) a command line tool for b) distributed working, so it really doesn't matter much which central web service you put in place, you can always get your local copy via
git clone REPO
.