Egregoros

Signal feed

API Docs
Timeline

Post

Remote status

Context

1
davidak

davidak

@davidak@chaos.social remote
Open link

The #gitea developers concluded after 10 years that it is not able to host its own development and that they depend on #GitHub.

https://github.com/go-gitea/gitea/issues/1029#issuecomment-4269181192

At the same time, the community fork @forgejo is self-hosted for a long time and is also powering the popular @Codeberg and at least 8 other public instances. So this seem to be a good time to migrate if you haven't already.

https://forgejo.org

Replying to @davidak@chaos.social
Now with 25% more charisma

Now with 25% more charisma

@feld@friedcheese.us remote
Open link
@davidak @forgejo @Codeberg disingenuous. They want some Github-specific features and to not have to deal with hosting infrastructure because they're developers not sysadmins/network engineers.

meanwhile Codeberg has had several DDoS/AI-crawler related outages. 4 months ago they were only hitting a 90% uptime... so I guess they're comparable to Github in that respect

but also it's hard to take their hosting infra seriously when they do stupid stuff like make their status page a subdomain of codeberg.org. This is a big nono, you always host your status page on a completely separate domain and ideally on a different Autonomous System

Replies

2
Replying to @feld@friedcheese.us
Replying to @mark22k@layer8.space