And because the damage extended to the .git project’s ‘objects,’ ‘refs’ and ‘logs’ folders, there was no way to recover the files and undo the catastrophe. The files were just gone in a puff of smoke.
I can sometimes be bad about pushing my inflight work, but I start getting anxious about it once I’ve reached a certain point. Like I might be brushing my teeth and be like, oh shit i should push that up.
Yep, make sure that you pushed somewhere on a private branch. But the new devs with their nocode-NoSQL-AI tools have a hard time understanding difficult concepts like “files” or “folders.”
Maybe I’m old fashioned, but I feel like programming tools shouldn’t blow away your checked in changes, even if you haven’t pushed yet. You do you, though.
Theoretically, they need tl be re-written every few years at most. Read everything off, format and re-write. Checking for corruption would be adviasable when you do it.
If you mean USB sticks (thumb drives), I have a few 20 year old ones that I dust off from time to time when all I need is something small. Some have been in a drawer for years before I touched them again.
My backup scheme is either Github or Google Drive, whatever I have uploaded in Discord DMs, and a snowballing pile of unorganized hoarded files, which One Day™ I will sort.
One thing you could do is buy the.largest external drive you can get on black friday sales. Then just copy everything in it. No sort. Just dump it all in there. Think of it like clearing the table unto a large garbage bag. Then unplug it, put it in the closet, and do it again whenever you remember.
Even a mess like that is better than no backup at all.
Good thing you added that. I’m so old-school/paranoid that I must have ownership of and physical access to the backup media to be able to count them as a backup.
If you don’t include .git/ in your backup you simply have no backup.
The .git folder is the heart of a Git repository. It is the hidden directory that Git uses to store all the information necessary for managing your project’s version control history. This folder is where Git keeps track of all the changes made to your files, allowing you to revert to previous versions, collaborate with others, and maintain a complete history of your project.
Funny story about those backups
No push to remote? If you’re working on something you care about you shouldn’t only have a local copy.
Image a git commit of 50k files. Lol.
Backups are for smart people. Not who we’re dealing with here.
Oh I’m aware. I’m just clarifying that a .git folder isn’t a backup lol.
What? But it says right there on the box. GIT = Great Interface for Takups
I can sometimes be bad about pushing my inflight work, but I start getting anxious about it once I’ve reached a certain point. Like I might be brushing my teeth and be like, oh shit i should push that up.
Yep, make sure that you pushed somewhere on a private branch. But the new devs with their nocode-NoSQL-AI tools have a hard time understanding difficult concepts like “files” or “folders.”
I am afraid to know what does that mean
Maybe I’m old fashioned, but I feel like programming tools shouldn’t blow away your checked in changes, even if you haven’t pushed yet. You do you, though.
A power surge or some other force majeure could though. Push your shit off site.
But what about the data gremlins?
Buy a service where you put your own git if you’re so worried about them.
And cave to the subscription imps?
I learned about thst that one day…
I learned the hard way
I was going to the high school of hard knocks when they offered me a scholarship to the college of hard knocks, I TOOK IT!
Knock knock
I’m here.
A local git repo is not a backup.
Git is just a folder
My backup scheme:
Computer --> 3 different cloud drives and github.
Also
Computer --> Wyoming home NAS --> USB external drive (weekly), swapped out every year and the old one stored in a waterproof gunsafe in the basement.
Wyoming home NAS --> Florida office NAS – > USB external drive (weekly)
Wyoming home NAS --> Austin office NAS --> Tape (monthly) --> IronMountain for 7 years.
If you are a single dev, all it takes is 14 USB sticks. 12 monthly backups and two for daily backups that you rotate weekly.
Just for my sanity, do you have to power up usb drives every so often or they corrupt?
Theoretically, they need tl be re-written every few years at most. Read everything off, format and re-write. Checking for corruption would be adviasable when you do it.
If you mean USB sticks (thumb drives), I have a few 20 year old ones that I dust off from time to time when all I need is something small. Some have been in a drawer for years before I touched them again.
My backup scheme is either Github or Google Drive, whatever I have uploaded in Discord DMs, and a snowballing pile of unorganized hoarded files, which One Day™ I will sort.
One thing you could do is buy the.largest external drive you can get on black friday sales. Then just copy everything in it. No sort. Just dump it all in there. Think of it like clearing the table unto a large garbage bag. Then unplug it, put it in the closet, and do it again whenever you remember.
Even a mess like that is better than no backup at all.
Good thing you added that. I’m so old-school/paranoid that I must have ownership of and physical access to the backup media to be able to count them as a backup.
I’m about to kick off a full offline backup of my GOG library over the holidays because I need that physical backup.
If you don’t include .git/ in your backup you simply have no backup.