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.

  • locuester@lemmy.zipEnglish
    1·
    3 days ago

    I use local Gitea hosted on a pi cluster. I only push open source stuff I want to share to github. Most of my code does not push there anymore. No reason to give them training data without compensation.

    My local gitea has its database and files on a NAS storage device, which encrypts and backs up to an AWS S3 bucket in another continent.

    • MyNameIsRichard@lemmy.ml
      1·
      2 days ago

      The compensation is the service you’re getting for free. It becomes more tricky if you’ve got a paid account. I don’t care if they train on my code because if they want to train on my crap, that’s their problem.