It’s been a fun ride, but I’ve had enough of GitHub for a while. The near constant outages, the vibe coding being shoved down everyone’s throat, the ai-first mentality… It’s too much for me to deal with. As of now, I’ve moved all of my mission critical stuff off of github, and onto codeberg.
Codeberg is a bit under the radar, but it’s getting more popular now that github’s been getting enshittified. Github is almost always the biggest option, with GitLab being a far second. Gitlab seemed like a good option at first, given how many big projects use it. However, it had the same pet peeve on it’s front page, where it advertises it’s ai powered development tools. If I wanted to use ai for my code, I wouldn’t be a programmer.
A very popular option among self hosters is, of course, self-hosting a git repo, like Forgejo, gitlab, or gitea. I used to use gitea, but after the corporate buyout… I’m a bit more hesitant. Even with the other 2, I’ve got one major hangup: most of the source configs for my server… can’t be hosted on my server. If my server goes down, I need a git repo to get it back up. If my git repo is hosted on my server, I’m shit out of luck. Unless I want to have a secondary cluster or a single point of failure, cloud hosted is my best option.
Yes, i’m aware that my switch, ethernet cable, router, modem, etc. are all single points of failure, that’s not important, bite me. Doesn’t matter. shoo, go.
Anyway, out of the remaining options… codeberg seemed pretty good to me. Fully open source (big ups!), good team, and not hosted in a corpo cloud. (every day, i stray closer to Silverhand)
Well, it’s sort of the straw that broke the camel’s back. Annoying AI buttons everywhere? Okay, i’ll survive, i can just avoid and disable them. Pull request spam? I haven’t been hit… yet. Server outage? Okay, surely that won’t be that bad, I just can’t use github for a few minutes. The thing that pushed me over the edge was that these outages would last for an hour or two… and happen nearly weekly. I’m sick of it, because it throws errors on my FluxCD system. Every failed pull causes issues, and I don’t want the state of my server to depend on whether or not GitHub decides it’s a good day or not. Codeberg has had some issues, especially with DDOS attacks, but they’re more rare, less severe, and they’re so much more open about it! The mastadon account posts updates, plans, and statuses whenever shit hits the fan, which is leagues above what github does. It’s like crawling into bed after walking on nails. Sure, there’s still problems, but I don’t feel left in the dark about it.
Well, not a lot. I’ll keep my github account, and leave up my repos on there as archives at worst. I’ve already got my more important projects set up as mirrors, so if codeberg does shut down, i’ve still got them on github. If anyone comes across them on github, they’ll still be able to see how often they’re updated, and with what, even if I haven’t logged in for weeks. My smaller stuff will just get archived, as it’s not going to be relevant to any programmers except myself. If anyone does care, it’ll still be up to date on codeberg. As of march 5th, 2026, not everything is migrated yet, but all the most important stuff is done. If you’re one of the weirdos who reads this blog, but doesn’t touch my code, nothing changes for you. The blog is still self hosted, self built, and open source if you’re that kind of nerd.
Honestly? I don’t know yet. Not many big projects that I care too much about are on here, so I’ll have to cope with github to work with them. I don’t if switching over is worth it for most people, but I’ll probably make a blog or mention about how it’s going in the future. For now, I’ve got a lot of work to do, and Codeberg seems like a wonderful aid in getting it done.
Stay caffeinated, I’ll see you on the ‘berg.
