this post was submitted on 25 Jul 2023
48 points (96.2% liked)

Selfhosted

38804 readers
594 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Would I have to do anything on my end, or would everything be set up automatically when the update is pushed?

all 22 comments
sorted by: hot top controversial new old
[–] [email protected] 15 points 1 year ago (2 children)

I have a selfhosted gitea instance, did I miss something? Gitea federation would be amazing!

[–] RegalPotoo 14 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 year ago

Right?! I’ve been waiting for GitLab to offer something like this for ages!

[–] SpaceNoodle 11 points 1 year ago (1 children)

Y'all update your services?

[–] Kalcifer 25 points 1 year ago (1 children)

Y'all don't update your services?

[–] [email protected] 3 points 1 year ago (2 children)

Ain't nobody got time for that.

[–] [email protected] 8 points 1 year ago

That's why you automated that when setting everything up

[–] [email protected] 1 points 1 year ago

Buddy! Renovate self hosted FTW with custom reflex manager for k8s yaml files using helm release. MAGNIFICENT

[–] [email protected] 10 points 1 year ago

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.

[–] [email protected] 9 points 1 year ago (1 children)

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.

[–] [email protected] 2 points 1 year ago (1 children)

Does Forgejo have any changes that differentiate it from Gitea yet? (apart from not being Gitea)

[–] [email protected] 1 points 1 year ago

Nothing realy exept licencing

[–] [email protected] 4 points 1 year ago

The setting option to enable it is already there, it just doesn't fully work yet.

[–] [email protected] 2 points 1 year ago

federated git! eeee!

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago) (2 children)

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.

[–] [email protected] 3 points 1 year ago (1 children)

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?

[–] [email protected] 1 points 1 year ago

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