Matt  Feb 25
Honestly, since my switch to Codeberg, I've had nothing but problems. It's down way more than a git service should be. And when it's not down, it's slower than molasses. I'm regretting my switch, I may go back to using gitlab or spin up a gitea server.
Show threadOrbitalMartianFeb 25

@thelinuxcast I agree that there is a lot of down time, but don't forget that it is a small nonprofit that run it alongside a number of other services such as a hosted Woodpecker CI, Translate, Pages, etc.

The uptime has gotten better over time and although inconvenient when it happens, it's not usually for more than a few hours.

I have never experienced any slowness with Codeberg, but that might be because I'm using old hardware which is slow anyway.

Show threadMatt  Feb 25
@orbitalmartian I get it that they're small, and if it had just been once or twice, I'd be with you. But this happens once a month or more. Or so it seems. That's not okay, no matter how small you are. Not if you want people to rely on your service.
Show threadClayton

@thelinuxcast @orbitalmartian I've been indifferent about my use. I know some projects I want people to assist with and the majority of people gravitate to GitHub... I keep some personal things at Codeberg. It's the git auth issue that gets me every time, and having to call git push twice to re-authenticate again.

Furthermore, I've also thought about using a Gitea service locally, even if it's just for git mirrors of my remote repos at GitHub and Codeberg.

Feb 25 at 7:34pmWeb