forgejo (gitea fork) should have federation i heard https://forgejo.org/2023-01-10-answering-forgejo-federation-questions/
I'd rather use forgejo than gitea anyway.
Didn't Gitea fork from gogs? What's the goto lightweight (so no Gitlab) self-hosted Git host nowadays? Difficult to keep track.
Yes, Gitea is a hard-fork of Gogs and started years ago. Forgejo is a soft-fork of Gitea when the primary authors of Gitea created a company of the same name to provide paid support (there's history there you can look up) but Gitea remains free and open source. Forgejo, supported by Codeberg, is a community fork and will upstream to Gitea.
Gitea/Forgejo is a great option, they recently even added build actions which are compatible with Github Actions.
No, Forgejo dorked feom Gitea
Had a hard time finding any recent information either, but with the recent release of 1.20 I've noticed that an Activitypub endpoint got added in the API and that permissions for it can be added to tokens. Seems very rudimentary so far though.
If you turn on Federation in Gitea app.ini settings then WebFinger will work. Nothing else is currently implemented.
Do you have a link to the year-old info for context? I'm curious why people would be interested in federation of a DVCS like Gitea et al?
git is distributed. but not issues, pull requests, forks... I think federation would provide all or most of that.
When I look at the download page, it seems active, 1.20.1 has been uploaded 2 days ago.
BTW Thanks for the question, I was using gogs, but that development seems to have halted. I'll try a migration to gitea.
The ActivityPub extension ForgeFed for federation between different servers is not finished yet. AFAIK Forgejo contributors work closely together with other ForgeFed devs to bring it forward.
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!