social.zlatko.dev

@zlatko It was even easier than that for the migrations I did - I mainly just needed to swap out the gitea binary for the forgo one and restart the service.

@zlatko depends on the version you currently on. If you are on a version of #gitea before 1.22.0, #forgejo should be a drop in replacement.

@hydrian mmm, 1.22.3. I'll have to see, I don't think we're using anything complex, maybe it'll still work.

@zlatko what issues are there with gitea? I set one up at work this year and if there's issues with it I'd rather change sooner than later.

@barbarossa no technical issues at all, everything works fine.

Longer story:

A while ago the Gitea team turned commercial, and they apparently did it in such a way that got a significant chunk of the community and a lot of the contributors worried. The usual "open core, private advanced functionality" thing, or some similar plan, but more importantly, they took complete control, and many maintainers got worried link
So they forked Forgejo, and even e.g. Codeberg made the switch, anticipating at least some enshitification like in e.g. Redis. At first it was just a soft fork, basically naming and some tiny things. But recently - start this year I think- there's a clear message about a hard fork. They'll be able to make some better fixes and pick their own direction. They'll still try to stay compatible but will but guarantee it. Another link

I don't mind one way or the other, but the community - at least the people I follow - seems to lean the Forgejo way, so I'm considering switching while it's still simple.

If you have your thing set up for work, you might be even better off with the commercially owned thing, you know, for support. But I'm running my instance for me and my friends, so I opt towards "maximum freedom that I can possibly get" kind of thing.

@zlatko https://forgejo.org/docs/latest/admin/upgrade/