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.

  • Cousin Mose@lemmy.hogru.ch
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    10 days ago

    It’s what happens to phrasal verbs when they become nouns and adjectives. I couldn’t find a great source other than this writing tip, but “back up” altogether makes up a phrasal verb.

    English is rather notorious for having these phrases that when translated directly don’t make any sense: the words on their own are rather meaningless and have to be taken together to derive the meaning:

    • speak up (verb)
    • slow down (verb) → slowdown (noun)
    • shut down (verb) → shutdown (noun)
    • piss off

    For example, I can’t translate “speak up” to “hablar arriba” in Spanish, that makes absolutely no sense.

    • Dave.@aussie.zone
      link
      fedilink
      arrow-up
      3
      ·
      9 days ago

      English is rather notorious for having these phrases

      English is essentially just a whole bunch of corner cases that its speakers agree on. Mostly.