Most companies rely on a SaaS based source control solution (GitHub, ADO, GitLabs, Codeberg, etc.). While this helps with issues are code loss from an individual POV (your laptop dies, you delete something). How do you back it up at scale should something happen to the service?

I know people, rightfully, joke about GitHub’s uptime, but what if it were to go hard down for an extended period of time?

So lemmings, how would you back up an organization’s source control?

Edit: a lot of people are focusing on personal or home. I’m wondering about corporate level without having on-premise resources.

  • dgdft@lemmy.worldEnglish
    13·
    11 days ago

    For the common-case risk model in the post body (SaaS user), the easy option is to set up a secondary git remote over SSH on a cheap cloud VPS. Then you can simply run git push backup-server or the like. Bonus points for setting up a cronjob to push to your backup box periodically, or to take periodic tarball snapshots of the repos on the server.

    Personally though: I self-host forgejo with registration disabled, and take automated snapshots with ZFS occasionally in case I truly bork things.