Gitea is light and fast so I highly recommend it. If you are worried about it being a for profit company, then use the fork, but if they haven’t done any harm, I’d said give them a shot.
if you have a hard time choosing between Gitea and Forgejo I recommend picking Gitea for now, as they haven't done anything bad just yet, but if they do Forgejo supports migration from Gitea.
iirc there isn't an official way of migrating the other way so if Forgejo fucks up you may end up out of luck
I’m on https://github.com/charmbracelet/soft-serve and like it very much. It couldn’t be any simpler. As long as you don’t need PR/MR features and full blown web UI it’s a really good choice IMHO.
I think the idea with soft serve us that you use hooks and use a dedicated ci/cd tool. I use adnanh/webhook for lightweight ci/cd on personal projects.
since 1.19 Gitea supports CI/CD action runners that are compatible with github actions. I have one that generates a static site from the data I store in gitea and publishes it to netlify.
I'm using Gitea. I did try OneDev and it is very nice, but mainly intended for single-team usage as it doesn't use different namespaces for user projects. It's also very much its own thing, with its own CI/CD for example. Gitea can integrate with other projects much better, like using Woodpecker for CI/CD or logging in with GitHub/GitLab using Oauth.
I did follow the drama around Gitea/Forgejo, but for now the Gitea company hasn't done anything wrong, there's no feature difference (Forgejo aims to be a soft-fork for the moment) and Forgejo had a bit of drama around the lead developer ~1 month after it was founded.
I assume that by now you've made a decision, so if I may I'd like to chip in and ask what's the benefit of self-hosting a Git instance, like the ones mentioned, over using existing free services like GitHub or Codeberg to host your code?
What do you gain by hosting this yourself, apart from privacy and security?
I'd say the main benefit gained is sovereignty and a sense of place. This is not for personal use, but rather for a computer enthusiast association that I'm part of, so having our own git to integrate with the rest of our services makes sense. Throw on branding and link it to our SSO.