On Monday, GoldenDog Linux made its first official public release, 2.1.32 “Golden Retriever”. Congratulations to Alexia and everyone who contributed. It is a real milestone: a new independent Debian-based distribution, built around a philosophy the site sums up as “built to stay out of your way.”
Shrug’s role in this is behind the scenes. We provide and operate the infrastructure that gets GoldenDog to its users: the package repositories, the ISO downloads, and increasingly the rest of what keeps a distribution reachable. Here’s what that has actually involved over the past week or so, because the gap between “we built a Linux distribution” and “people around the world can download it and keep it updated” is full of unglamorous engineering that nobody writes launch posts about.
There’s more to releasing a distro than building an ISO
Making a Linux distribution available to the public introduces a different set of problems from building one.
Users need somewhere to download installation images that does not fall over the first time a release gets attention. They need package repositories that stay available so every installed system can keep updating. Those services have to survive traffic arriving from multiple continents at once, over HTTPS, with valid certificates that do not expire mid-release. And somebody has to maintain, monitor, and secure all of it for as long as people depend on it, whether or not anyone is paying attention that day.
For an independent project, those requirements get expensive quickly. Alexia had a clear principle from the start: GoldenDog would remain free, and access to it and its updates wouldn’t depend on users paying or donating. The infrastructure has to fit inside that constraint rather than fight it.
From one origin to a distribution network
When GoldenDog’s APT repository moved onto shrug.host back in May, it was a single server in Sao Paulo handling repository and download traffic. That was fine for a project pre-release. It was not what you want to be standing on the week a distribution ships to the public.
Over the past week we expanded it into a regional serving footprint: an origin in Sao Paulo, serving regions in North America and Europe, with geographic DNS steering live in front of them. The systems are managed declaratively, so the configuration that makes each region work lives in reviewable, reproducible definitions rather than in someone’s memory. Certificates issue and renew automatically. The serving fleet has its own observability, separate from everything else we run.
Some of this is still in progress. The regional nodes currently reverse-proxy content that ultimately comes from the origin, and we’re working on regional content mirroring so each region can serve independently. That’s the next step, and like everything in production, it lands when it’s verified, not when it’s announced.
Why we do this
Shrug.host exists partly because we believe independent projects should have access to professional infrastructure without having to build a hosting company themselves. GoldenDog is a good example of what that looks like in practice: Alexia and the contributors focus on building the distribution, and we take responsibility for the systems that deliver it.
It’s not the only way to support open source, but it’s the one we know how to do well.
Congratulations again to Alexia. We’re glad to be the infrastructure behind GoldenDog, and we’re looking forward to seeing where the project goes next.
Explore GoldenDog Linux: goldendoglinux.org
More on our GoldenDog hosting work: shrug.host/open-source/goldendog/
Shrug’s open-source hosting generally: shrug.host/open-source/