81–87 of 87 posts
What are the current thoughts on Gitea vs Forgejo? I'm thinking of migrating from a self-hosted Gitlab to one of them in the near future. The way Gitea was taken over leaves a bad taste in my mouth so I'm leaning towards Forgejo, but it's not really clear to me if that's the right choice.
edit: looks like Forgejo is already talking about Actions support https://forgejo.org/2023-02-27-forgejo-actions/
Really excited for Gitea Actions!! Will probably look into switching from GitHub now. Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system.
> Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system. I'm in the opposite camp, especially when this separate system is as simple as Drone CI or Woodpecker CI (I mostly use the former, but the latter is more permissive, license wise). I came to holding this view after I ran into some issues by using a self-hosted GitLab Omnibus install previously: https://blog.kronis.dev/articles…
Earlier quoted context omitted.
> It's going to take a long time until they begin to match the Gitea momentum. I'd hope so! I am not interested in many of the features being added to Gitea (i.e. the momentum you allude to[1]). I want a light binary I can continue to self-host on a Raspberry Pi Zero that doesn't have Docker installed. 1. I feel Gitea is being positioned as a competitor to GitHub and GitLab - good for them! However, the previous iter…
> (i.e. the momentum you allude to[1]) The momentum stalled when the community was plagued recently by toxic behaviour of one of the members who started the fork. He had to step down from the "well-being" team[1], bullied a moderation team member into stepping down[2] and forced him to disclose information from a private chat[3]. Now he is trying to "reboot" the community to erase his previous bad behaviour [4] Forge…
Really excited for Gitea Actions!! Will probably look into switching from GitHub now. Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system.
> Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system. I'm in the opposite camp, especially when this separate system is as simple as Drone CI or Woodpecker CI (I mostly use the former, but the latter is more permissive, license wise). I came to holding this view after I ran into some issues by using a self-hosted GitLab Omnibus install previously: https://blog.kronis.dev/articles…
This situation is actually a bit more insidious. All these CI/CD features are just a thinly veiled attempt at locking users into the platform. There's not big money to be made selling git hosting, but if you control how the software is built, then you have made yourself a hard dependency. If you look at the starter workflows they provide, they encourage bad practices where your application build is defined in their DSL. Experienced programmers might steer away from such usage, but many novice won't. If you have enough novice adoption, it becomes the norm. So many projects these days cannot even be built locally without a CI service dependency, where instead 99% of the time, all you needed was a simple makefile.
Really excited for Gitea Actions!! Will probably look into switching from GitHub now. Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system.
Gitea actions looks neat though I'm not sure how you are meant to run windows or mac-centric workflows with it since the runtime (nektos/act) seems to require docker. If its not possible that might limit its usefulness somewhat...
Alternatively, I was wondering if it supported podman. I prefer podman in most cases since it runs without root and doesn't mess with my host's nftables. Docker always invokes iptables and adds a bunch of chains/rules. Grrr...