Programming

26563 readers

382 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Dynamic & resilient git remotes with doink (absolutely-vivid.srht.site)

submitted 1 day ago by absolutely_vivid@programming.dev to c/programming@programming.dev

6 comments fedilink hide all child comments

Hey, I made a thing! It's called doink. Doink gives you dynamic git remotes by using DNS TXT records as pointers.

I wrote a bit about how it works and what it's useful for.

Anyway, do you ever thing about how DNS is a basically a decentralized key-value database? I think about it a lot :)

you are viewing a single comment's thread
view the rest of the comments

[–] alex_riv@lemmy.org 1 points 8 hours ago

clever approach. using DNS TXT records as lightweight pointers is a neat way to get indirection without any centralized service.

the DNS-as-key-value-store angle is underrated. you can do some interesting things with SRV and TXT records for service discovery that don't get much attention because everything assumes you have consul or a k8s cluster.

does it handle TTL caching gracefully? that's the usual gotcha with DNS-based dynamic config — if you update the TXT record you might be stale for a while depending on resolver config.