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.
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.
Came for the snippet, stayed for the explanation.
We run this in production at a fairly large scale and can confirm the caveats are real.
It should work without shell access, you just lose the command-line shortcuts.
The quote in the middle is doing a lot of work here, and it earns it.