Would I have to do anything on my end, or would everything be set up automatically when the update is pushed?
I have a selfhosted gitea instance, did I miss something? Gitea federation would be amazing!
https://github.com/go-gitea/gitea/issues/18240
First I’m hearing about it as well - definitely an interesting idea, just hope that it’s opt-in
deleted by creator
Do you net set your private repos to private? My public stuff is public and private stuff is private.
It’s more about people being able to interact with your public projects without having to sign up to your instance. I’ve been wanting this for a few tools that I create and maintain. It’s awkward for people to open issues if they can’t sign up to my gitlab instance
I made my instance accept public sign up. Through now that I think about it, my email setup is probably broken, because I changed something.
Right?! I’ve been waiting for GitLab to offer something like this for ages!
It’s too early to know how exactly it’ll be implemented, but I’d bet there would likely be a toggle/setting to turn on at the very least. I’m sure the upgrade instructions will be early laid out how to enable it.
Y’all update your services?
Y’all don’t update your services?
Ain’t nobody got time for that.
That’s why you automated that when setting everything up
Buddy! Renovate self hosted FTW with custom reflex manager for k8s yaml files using helm release. MAGNIFICENT
Maybe consider using forgejo (gitea fork used by codeberg)
And i do think, some changes would be needed but nothing big, also it wouldnt ne activated by default.
Does Forgejo have any changes that differentiate it from Gitea yet? (apart from not being Gitea)
Nothing realy exept licencing
The setting option to enable it is already there, it just doesn’t fully work yet.
federated git! eeee!
You’d have to be significantly more careful with backups, as it’s really easy to effectively “burn” a domain from federating over AP ever again (at least to instances that federated with it before), but otherwise it should be reasonably automatic as federation gets implemented piece by piece.
As someone who has very little experience with ActivityPub but is always interested in learning more, what’s the risk of "burn"ing a domain? Does it come from certs or signatures changing on the same domain, causing it to no longer be accepted or something?
it’s partly because everything has public/private certificates, but also partly because there isn’t much synchronization going on after the initial “push”. if you shut an instance down and modify the database directly without informing other instances (say, you remove an account) then other instances will not be able to tell and will drift out of date, essentially making that specific thing unusable for any instance that has previously interacted with it. if you expand that out to, say, wiping and re-creating an entire database, then you end up with so much uncertainty that you may as well start over from a fresh domain
As someone who has very little experience with ActivityPub but is always interested in learning more, what’s the risk of "burn"ing a domain? Does it come from certs or signatures changing on the same domain, causing it to no longer be accepted or something?
