this post was submitted on 24 Jan 2024
270 points (90.9% liked)

Open Source

31365 readers
158 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
 

First, they restricted code search without logging in so I'm using sourcegraph But now, I cant even view discussions or wiki without logging in.

It was a nice run

you are viewing a single comment's thread
view the rest of the comments
[–] d3Xt3r@lemmy.nz 149 points 10 months ago (4 children)

Just so you're aware, Gitea was taken over by a for-profit company. Which is why it was forked and Forgejo was formed. If you don't use Github as a matter of principle, then you should switch to Forgejo instead.

[–] scrubbles@poptalk.scrubbles.tech 54 points 10 months ago (3 children)

Damnit of course it was. Thanks for letting me know, now I'll have to redo my 100+ repos.

[–] moreeni@lemm.ee 18 points 10 months ago (1 children)

Changing the remote should be fairly trivial with enough bash skills

[–] scrubbles@poptalk.scrubbles.tech 6 points 10 months ago (1 children)

It's more I don't have them all checked out, and a good chunk are mirrors of github, so I'll have to list out each one and push to a new remote, mirrors will have to be setup again, and I also use the container and package registries. I'm pretty embedded. It's not impossible, but it's a weekend project for sure.

[–] zeluko@kbin.social 3 points 10 months ago* (last edited 10 months ago) (1 children)

If it was just forked, cant you just switch the package/container-image and be done?

[–] scrubbles@poptalk.scrubbles.tech 2 points 10 months ago (2 children)

Depends on how much it was changed I'm guessing. Fingers crossed I could just flip it over, but who knows

[–] stardreamer@lemmy.blahaj.zone 2 points 10 months ago

Simply changing the binary worked for me. Been more than 1 month and no migration issues.

It does still show gitea branding, however.

[–] PowerCore7@lemm.ee 1 points 10 months ago

If you are using containers, it should be fairly trivial. Otherwise, there might be some renaming to do, but Forgejo should be 100% compatible with Gitea (at least right now). Just make sure you have a good backup in case anything would happen.

[–] NightAuthor@lemmy.world 3 points 10 months ago

If there’s a fork, it’ll probably be an easy migration/in-place upgrade.

[–] lambchop@lemmy.world 1 points 10 months ago

My understanding is the fork isn't doing much but waiting to see if gitea turns to shit, pushing all their changes upstream. If you use docker I've heard you can just pull the new image and it simply drops in, no migration needed.

[–] aniki@lemm.ee 4 points 10 months ago (1 children)

did they get federation working?

[–] d3Xt3r@lemmy.nz 14 points 10 months ago (1 children)

Nothing usable yet unfortunately, but they seem to be making good progress: https://codeberg.org/forgejo/forgejo/issues/59

[–] aniki@lemm.ee 5 points 10 months ago

Thanks for the link! As long as it's being worked on I feel comfortable spinning up an instance. I've been meaning to do gitea for a while so I'm glad I waited.

[–] JoeKrogan@lemmy.world 2 points 10 months ago

Thanks for the info

[–] Hexarei@programming.dev 2 points 10 months ago

Oh man, thanks for this. I had no idea, having used gitea for years now.