Say ww3 kicks off and power goes off - how are you keeping your servers up? Solar panels and batteries?

What if there’s a biblical flood and you dont have the means to build an arc? All your servers are destroyed beyond repair?

What if you heard the Feds are coming to cart you and your servers away cos they suspect you of bad mouthing Emperor Tromp? (you’re on the run or subject to months of torture and yeah, you’re never getting your kit back)

What if theres a war and Luxembourg (you know, the enemy) let’s of an EMP pulse that kills your servers and all the infrastructure (power, internet…). How do you access all those cherished pics on Immich?

I’m not suggesting any of this will/can happen, its all just for lols, but have you made any contingency plans? Big binders full of printouts, bug-out bags, those flower-type solar things that track the sun, Faraday cages…

  • Andres@social.ridetrans.it
    link
    fedilink
    arrow-up
    2
    ·
    3 days ago

    @somegeek @jobbies This is a good read. I was rather amused by your “TODO: How to use Git offline? Offline merge requests?” section, though. Git was written by people who literally email each other patches. It’s offline-first, with online stuff tacked on there. You can copy a cloned git repo to a usb stick and give it to someone, and now they have the entire history. Of course merge requests and bug tracking are separate (I understand what you meant w/ the TODO), but git itself is already there.

    • Alavi@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      Thank you! I actually got that figured out during the second war but didn’t got the time to update the post. I put what I learnt in my knowledge base linked below. I will uodate the post. Thank you for pointing that out!

      I tried to push it at work but most of my team members didn’t felt like learning this whole new workflow (they’re “normies” you could say. Using windows, outlook, etc.)

      http://kb.alavi.me/#/page/git email workflow