3 ms·

previously discussed here: https://news.ycombinator.com/item?id=46064571 https://news.ycombinator.com/item?id=46064571 Migrating the main Zig repository from G

• aatd86 10mo ago
  Didn't know about codeberg and can't even access it... Is it https://codeberg.org/ https://codeberg.org/ ??
  • politelemon 10mo ago
    That is correct. It is down quite a bit. https://status.codeberg.org/status/codeberg https://status.codeberg.org/status/codeberg
    • testdelacc1 10mo ago
      92% uptime? What do you do the other 8% of the time? Do you just invoke git push in a loop and leave your computer on?
      • some_furry 10mo ago
        As discussed elsewhere in this thread: They're under DDoS, and have been very public about this fact.
      • badsectoracula 10mo ago
        You keep working since Git is decentralized. You can also run a Forgejo instance (the software that powers Codeberg) locally - it is just a single binary that takes a minute to setup - and setup a local mirror of your Codeberg repo with code, issues, etc so you have access to your issues, wiki, etc until Codeberg is up and Forgejo (though you'll have to update them manually later).
        • sundarurfriend 10mo ago
          I hope Codeberg is able to scale up to this surge in interest, but > it is just a single binary that takes a minute to setup - and setup a local mirror of your Codeberg repo with code, issues, etc so you have access to your issues, wiki, etc is really cool! Having a local mirror also presumably gives you the means to build tools on top, to group and navigate and view them as best works for you, which could make that side of the process so much easier. > you'll have to update them manually later What does the manually part mean here? Just that you'll have to remember to do a `forgejo fetch` (or whatever equivalent) to sync it up?