Comment by thewisenerd
Comment by thewisenerd 3 hours ago
previously discussed here: https://news.ycombinator.com/item?id=46064571
Migrating the main Zig repository from GitHub to Codeberg - 883 comments
Comment by thewisenerd 3 hours ago
previously discussed here: https://news.ycombinator.com/item?id=46064571
Migrating the main Zig repository from GitHub to Codeberg - 883 comments
That is correct. It is down quite a bit. https://status.codeberg.org/status/codeberg
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?
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).
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?
As discussed elsewhere in this thread: They're under DDoS, and have been very public about this fact.
Didn't know about codeberg and can't even access it... Is it https://codeberg.org/ ??