Linux

Yes it is, federation work is ongoing. I think stars are in beta.

You do realize git is federated right? That's how it came about.

As for Forgejo itself they are working on instance to instance federation. I think it is Activity pub based so theoretically it could be compatible with Lemmy.

Docker Gitea to Docker Forgejo was basically using a different image and pointing it to the existing database. Not sure if and when both will be different enough for that to no longer work. But I also only use it as a docker compose storage repository. No idea about automation etc.

I don't think I did more than spinning up the Forgejo container. Using the same db container and everything.

I followed the directions and it worked. No issues and no regret.

Check their website for migration info. There are some caveats in special circumstances but most people can just change the docker image from gitea to forgejo.

I did exactly that with no issues.

if i remember correctly, i just replaced gitea with forgejo for image: in my docker-compose, and it just worked

it was a couple of versions back, so i don't know if that still works

I don't know how to read the phonetics but they're going for forĝejo which is for-jey-o, so I'd imagine that's how it's pronounced.

4-J-yo

forgejo is like github copy, and is a fork of the relatively known gitea. so far there are no federation features

radicle is something similar, but as I understand, with distributed repo management. I don't know the implications of this.

radicle also has an own cryptocurrency, and is entangled with web3.
while not all cryptocurrencies are scams, and probably the same applies to web3 projects, almost all of them are either scams, or useless for the purpose of using it as a currency. I don't know how the radicle currency fares, but it made me distrust them somewhat when they started talking about that in their announcement channel, and the fact that since then the channel did not post much else did not help to gain back this trust

Forgejo started as a fork when Gitea became a commercial company with unknown intentions

Well, aren't you glad they're removing go-git then!

To be fair, they supported two different git backends, one of them being go-git which was the one corrupting repositories. However, it was never enabled by default, you specifically had to build Forgejo with a specific tag to instead use that as the backend. If you just built normally or pulled ready-made containers or bins then it was always the default git backend.

It's interesting that Forgejo ran better than Gitea considering it's a fork.

I'm not sure it makes much sense that gitea is a bit too heavy, but forgejo (a fork of gitea) runs perfectly. But forgejo appears to have more developments momentum as a project and so you probably landed on the right choice anyway. 🙂

Do you use it for anything other than syncing code? Currently I'm using plain SSH sync for all my personal git repos, and I'm not sure if there'd be any advantage in switching to Forgejo.