New series: what assistive tech really hears on your checkout page. Start with part one →
Shipwright
Home
DevOps Jul 3, 2026 2 min read 222 views

Inside Our Home Lab: Racks, Cables, and a Very Loud Switch

Elias Lindqvist

Elias Lindqvist

@eliaslq

Share
Cover illustration for the article Inside Our Home Lab: Racks, Cables, and a Very Loud Switch

Photos from the small cluster we use to test deploys before they reach the cloud. The best deploys are the ones nobody notices. Everything in this post exists to make releases small, reversible, and dull enough that we can ship on a Friday afternoon.

The 12U rack before cable management
The 12U rack before cable management
Patch panel, labelled at last
Patch panel, labelled at last
Three mini PCs running the cluster
Three mini PCs running the cluster
The very loud 24-port switch
The very loud 24-port switch

Inside the rack

Our pipeline runs the same steps locally and in CI: install, lint, test, build, and publish an image tagged with the commit hash. If a step cannot run on a laptop, it does not belong in the pipeline.

We will revisit this in six months with fresh numbers. If the results change, we will update the post and note what changed at the end.

If you try this on your own project, start with one page or one service rather than the whole codebase. A small experiment gives you real numbers to argue with, and it is easy to roll back if the idea does not fit.

We have been running this approach for several months now. The initial setup took about a day, and the ongoing cost is close to zero once the team knows where to look.

None of this is new, and that is the point. The techniques that last are usually the boring ones that are documented well and supported by the platform itself.

As always, the examples are simplified to fit on a page. The production version has more error handling and logging, but the shape of the code is the same.

What we would change next time

None of this is new, and that is the point. The techniques that last are usually the boring ones that are documented well and supported by the platform itself.

  • Tag images with the commit hash.
  • Make every deploy reversible in one command.
  • Alert on symptoms, not causes.
  • Review infrastructure plans like code.
Elias Lindqvist

Elias Lindqvist

Author

Platform engineer who keeps the pipelines green. Elias writes about CI, containers, and the observability you only miss at 3 a.m.

Related Posts

Comments 4

Priya Raman Member

Came for the snippet, stayed for the explanation.

Yuki Tanaka

We run this in production at a fairly large scale and can confirm the caveats are real.

Priya Raman Member

It should work without shell access, you just lose the command-line shortcuts.

Oskar Nilsson

The quote in the middle is doing a lot of work here, and it earns it.

Leave a comment

Your email will not be published. Sign in for a faster experience.

Supports **bold**, *italic*, and `code`.