Infrastructure defined in a repository
Built the company's own infrastructure as 19 Ansible playbooks and
34 roles across 12,065 lines of YAML, converging a live host to a
declared state with every play idempotent.
August 2026

Situation. Engineer ApS maintains its own infrastructure as code.
The repository covers deployed public services and the configuration
of other components, including backup and mail automation whose
operational activation is a separate step. Capturing that scope in
code makes the setup inspectable rather than dependent on memory.

Task. The whole estate had to be described in a repository rather
than in a head, and described in a form that converges a real host
rather than documenting one.

Action. The recorded implementation comprises 19 playbooks and 34
roles across 12,065 lines of YAML; these figures describe that
recorded stage, not the current repository size. The shape matters
more than the size. Composition is data rather than flags: a host
sits in a tier group whose variables declare which roles it runs, so
provisioning with no arguments converges every host to its declared
state. Idempotence is a contract rather than an aspiration — a
converged host reports zero changes, and a play that cannot say that
is not finished. Four command namespaces keep the promises apart: a
gate that touches no host, reports that read one and never change
it, provisioning that changes a host to match the repository, and
verification that changes a host on purpose and returns a verdict.

Result. The repository supplies the configuration for rebuilding the
declared environment, and the parts of it that were only ever true
because somebody remembered them are now assertions that fail a run.
The cost is real: every change is slower to make than editing a file
on the server would be, and a converge that half‑applies is worse
than one that refuses, which is why a preflight play was later added
in front of it. That trade was made deliberately and it has held.

Categories:
1Platform Architecture	/categories/platform-architecture/	engineer.company	70
1DevOps	/categories/devops/	engineer.company	70
1Infrastructure	/categories/infrastructure/	engineer.company	70
1Automation & CI/CD	/categories/automation/	engineer.company	70
1Reliability & Backups	/categories/reliability/	engineer.company	70
1Linux & Servers	/categories/linux/	engineer.company	70
1System Administration	/categories/system-administration/	engineer.company	70
1Documentation	/categories/documentation/	engineer.company	70

Services:
1Cloud Infrastructure & Migration	/services/cloud-infrastructure/	engineer.company	70
1Infrastructure as Code	/services/infrastructure-as-code/	engineer.company	70
1DevOps & CI/CD Automation	/services/devops-cicd/	engineer.company	70
1System Administration	/services/system-administration/	engineer.company	70

hThis page on the web	URL:https://engineer.company/portfolio/servers-you-can-rebuild-from-scratch/	engineer.company	70
