- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Keep in mind if you’ve pinned your docker-compose.yml as they suggest in the installation guide, you’ll want to increment that.
Keep in mind if you’ve pinned your docker-compose.yml as they suggest in the installation guide, you’ll want to increment that.
Does Forgejo have any killer features or something that makes it worthwhile for me to switch away from Gitea now?
Actions is significantly better, there are lots of subtle UI improvements, there are new importers, etc. Not a killer feature, but many small improvements that add up.
Thanks!
The longer you wait the more incompatible and harder to migrate it will get.
While right now the features have not diverged that much, only Forgejo is working on federation and due to license incompatibility it will not be possible to back-port that to Gitea.
I know, but I thought it was already too late to simply change the docker image and be done with it. But, you are saying it’s still just a drop-in replacement currently?
Depends on the version you’re running.
https://forgejo.org/docs/latest/admin/upgrade/from-gitea/
I’m out of luck, it seems, since I’m already running Gitea 1.24.6.
Not anymore, but afaik it is still possible with some not so bad manual work.
Not being run by corporate overlords
Seriously though, the community is a lot healthier
By the way you framed you question sounds like you are looking for an excuse to move away from gitea
By the way you framed you question sounds like you are looking for an excuse to move away from gitea
not really. it is more of, “i am not really motivated enough right now, can you please motivate me a bit?”
I meant it more like “I’m concerned if I’m missing out on something huge by still using Gitea.”
But if they’re still mostly the same, I’ll just stick with what I’ve already set up.
as others have said, major thing is federation, which is rolling out. other than that, the are mostly complete.