270

submitted 9 months ago by antrosapien@lemmy.ml to c/opensource@lemmy.ml

126 comments fedilink hide all child comments

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

[-] scrubbles@poptalk.scrubbles.tech 82 points 9 months ago

Honestly for selfhosters, I can't recommend enough setting up an instance of Gitea. You'll be very happy hosting your code and such there, then just replicate it to github or something if you want it on the big platforms.

[-] d3Xt3r@lemmy.nz 149 points 9 months ago

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 9 months ago

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

[-] moreeni@lemm.ee 18 points 9 months ago

Changing the remote should be fairly trivial with enough bash skills

[-] scrubbles@poptalk.scrubbles.tech 6 points 9 months ago

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 9 months ago* (last edited 9 months ago)

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

[-] scrubbles@poptalk.scrubbles.tech 2 points 9 months ago

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 9 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 9 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 9 months ago

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

[-] lambchop@lemmy.world 1 points 9 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 9 months ago

did they get federation working?

[-] d3Xt3r@lemmy.nz 14 points 9 months ago

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

[-] aniki@lemm.ee 5 points 9 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.