Mastodawn

Great news: Today, we have managed to distribute our Forgejo instance across two servers. A main instance still handles most traffic, but requests from #CodebergPages are now handled by another server. Going forward, we'll try to route more read-only traffic there to distribute the load.

This is an important milestone, because such a setup was never tested with #Forgejo at this scale.

This should improve availability of both Codeberg.org and Codeberg Pages.

Details: https://codeberg.org/forgejo/discussions/issues/259

Show thread

Gusted Oct 28

@Codeberg To expand on the improved availability.

Codeberg pages does not rate limit requests, so it was entirely possible for a scraper or malicious user to send too many requests and slow down codeberg.org.

Traffic is now redirected to a separate Forgejo instance that currently only affects the availability of Codeberg pages and not codeberg.org as a whole. Because Codeberg Pages now has an entire Forgejo instance to itself, it should naturally be much more difficult to bottleneck this instance, their availability should be better.

Show thread

Fritz Adalis Oct 28

@Codeberg @kevin
Wait... you ran all that on only one server?

Show thread

Gusted Oct 28

@FritzAdalis @Codeberg Codeberg currently uses three servers to operate its services. Forgejo (the software that powers codeberg.org) and Codeberg pages were already running on separate servers for quite some time.

What we did today was to create a new Forgejo instance in a read-only mode (see the linked issue) that Codeberg pages now uses, this instance is run on the same server as Codeberg pages.

Show thread

Fritz Adalis Oct 28

@Gusted @Codeberg
Still impressive to run a public service on just a couple of machines.

Show thread

Gusted Oct 28

@FritzAdalis @Codeberg We run it bare-metal and it's "old" and donated hardware. It's kind of amazing to still see so much use of these hardware that was otherwise e-waste.

Show thread