I have Forgejo working pretty well. I also have a Forgejo runner running workflows successfully using a Docker-in-Docker system running in Kubernetes. This works pretty well and I like it, but I'm starting to run into some challenges with more advanced workflow use-cases.

For example, I only have one runner so jobs stack up. I wasn't sure how to implement multiple runners given that each runner needs to save a static token. I saw some references to ephemeral runners. Does anybody use auto-scaling or multiple-instances such as with ephemeral runners?

Additionally, using docker-in-docker has some issues. The Docker daemon gets persisted across jobs so the output images stack up and I have to periodically run docker system prune inside the runner. Trying to run docker commands that require logging in inside the workflow also conflicts with Forgejo's own control of the Docker Daemon.

Does anybody else run into these kinds of issues and have a good strategy? There was this issue about using firecracker micro-vms which could have fixed the d-in-d issues, but no recent updates.

My instance is getting pummeled by scrapers crawling nonsense. Like issue and pull searches with every single variant of label combinations.

Everything's coming from a shitload of different residential IPs at a very fast cadence.

There's just not that much content on my instance to warrant this traffic. It could be scraped in a minute or two like this if it were legitimate traffic.

A new version of Forji, the iOS app for Forgejo is released. New features are

• a persistent cache for issues, PRs and repos to make working with slow instances like Codeberg more pleasent.
• a merged instance view, where items from multiple Forgejo instances can be viewed at once.
• a filter in the repo view to filter archived or mirrored repos

Forji is free and open source under GPLv3 and hosten on Codeberg https://codeberg.org/secana/Forji

Forji is an iOS app for Forgejo, like the Github App is for Github. It works with self-hosted instances and public once like Codeberg. It landed in the App Store today. Fully open source under GPLv3 with the code here: https://codeberg.org/secana/Forji

Got to check out their booth at KubeCon and they shared the stuff they used for auto deploying their demos. Saw this gem in there.

For context this a fleet config to have it pushed to downstream clusters managed by Rancher

What's going on @organicmaps@fosstodon.org? Have you gone back to github?

Edit link to forgejo repo: https://git.omaps.dev/organicmaps/organicmaps

Edit2: The project was forked https://codeberg.org/comaps/comaps

Currently https://en.wikipedia.org/wiki/Forgejo redirects to the sub-section of Gitea article. Would it be time to write a whole Forgejo article?
What information / sections should be included in it?

https://codeberg.org/forgejo/forgejo/src/branch/forgejo/release-notes-published/7.0.15.md