This was originally a Twitter thread, but long-form text is way less painful. Tonight’s rant sponsored by lukewarm Thai food that should have been inside me about 3 hours ago.Continue reading
What the Sporks? How We Built a Reasonably Competent Blog
After being successfully up and running for over a year with very few major changes needed, now seems as good a time as ever to break down how sporks.space runs, what secret sauce we use to run it how we like it, and so forth.Continue reading
What’s on my (alyx’s) desk?
Inspired by cb’s post earlier this week, and by the same friends’ musings, I felt it would be fun to go over what my every day equipment is. This probably won’t convince you to use it, but serves more as a clarification of why I use it. With that out of the way, let’s talk about what’s on my desk.Continue reading
DNS as Code with DNSControl and GitLab
With the “infrastructure as code” renaissance, managing infrastructure has never been easier. Every change is easily recordable and reproducible and, because it’s all code, it’s never been easier to store a history of what’s changed to easily review in
But short of running your own DNS servers and running custom scripts to convert code into a BIND zonefile, it’s historically been hard to manage DNS in the same way – so often, even though the servers themselves are easy to change, managing DNS means connecting to Route53, or Cloudflare, or any of a myriad of different domain registrars and DNS providers and manually changing fields in their application with no easy way to propagate changes across multiple domains or to roll back to a historical record if a new change causes something to break.
Using a tool like DNSControl, which allows a provider-agnostic view of DNS records as code, along with automatic capabilities to update records at your provides, fixes all of this.Continue reading