Thinking about recreating my common Homelab CI pattern to use prefixed PR labels to pick available actions-jobs/ansible-task to run.
It would then let some decoupling happen from automatic digest updates with intentional actions. Not sure if that's a good or bad thing yet but it'll be something to explore. Renovate could also merge things like Git submodules and Forgejo packages without triggering Ansible host runs.
Existing solution is rigid in predefined tasks in the action job YML. Worked great to get things initially into IaC. Now the constant digest updates and small changes across so many little mini hosts is causing kind of a bit of churn on external hosts. Should work to reduce this through more mirroring and caching for quick gains.
FYI, even though the #Forgejo and #Gitea docs brand "MINIO", it will still work for other S3 compatible vendors. If you just mentally s/MINIO/S3, the rest makes sense.
TIL what the actual relationship between #Forgejo and #Gitea is (currently, the former soft forks the latter, layering their patches on top; they may hard fork later this year) and also how to pronounce the former (it’s Esperanto, see https://forgejo.org/faq/#where-does-the-name-come-from)
Until now I had assumed (due to lack of context in online mentions of the project) that Forgejo was a completely separate project!
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
Forgejo may become a hard fork of Gitea; user research is on the way to figure out the scope of moderation in Forgejo instances; a new requirement for tests was added to the development workflow; the "You pushed on branch" user experience was improved; the migration of translations to Weblate began.
Da habe ich mich nun seit ein paar Tagen mit #gitea beschäftigt nur um heute festzustellen, dass die kommerzialisiert wurden und es einen #Fork namens #forgejo gibt.
Glücklicherweise sind die beiden noch nicht wirklich weit auseinander, so dass die ganzen Gitea Tutorials noch funktionieren.
Added custom css to @forgejo to load Monaspace Neon as a font on @catppuccin Frappe Green <3 great combination. But I must only patch my avatar to have better visibility :) #git#gitea#forgejo
New blog post: my experience contributing to #Forgejo. I'll continue doing more of those reports to evaluate the #onboarding processes in #FOSS projects.
Hm. It seems I cannot create a hierarchy of teams and projects in #forgejo the way I can in #gitlab. In the forgejo/gitea world you have organisations and teams. But you cannot have teams under teams. Which is a bit limiting, IMHO. Or am I missing something?
I'm moving away from #gitlab on my #homelab. It's not that I don't like it, I do. A lot. But it's way too much for my humble needs, so I moved all my local repos to #forgejo with #woodpecker for CI/CD.
I just finished the pipeline that builds and publishes my blog and it's working nicely.
#TIL that @forgejo is not a simple soft-fork of #Gitea anymore and they have diverged and improved quite a bit since a for-profit company bought Gitea and they changed their mission. They are also on the way to bring #ActivityPub to the platform. This is quite interesting.
@Mehrad Is not not? The comparison page you link on the @forgejo webpage still says it's soft, and last time I saw this discussed on https://matrix.to/#/#forgejo:matrix.org on January 3rd it sounded pretty much like it's still a soft fork.
Stars should still go to Forgejo, if you're participating in that game :-)