From 07ca8f2e3dc0c712402115e8b88e972516757ed1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Arnaud=20Pr=C3=A9mel-Cabic?= Date: Mon, 1 Jun 2026 10:17:42 +0200 Subject: [PATCH] docs: add title and abstract to README Co-Authored-By: Claude Opus 4.8 (1M context) --- README.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index af05031..8db8218 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,17 @@ -# Configuration as Code — Puppet vs Ansible vs Terraform +# Configuration as Code: Terraform, Ansible & Puppet — The Three Musketeers of Infrastructure Presentation for the **Finistère Dev Meetup**. +## 📝 Abstract + +> "It works on my server." One machine, hand-configured, impossible to reproduce — and the problem only gets worse as you scale to ten, a hundred, a thousand servers. Configuration drift creeps in silently, and nobody remembers exactly how anything was set up. +> +> What if your infrastructure was just… code? +> +> This talk introduces **Configuration as Code** through its three best-known tools — **Terraform**, **Ansible**, and **Puppet**. We'll see what each one actually does: how Terraform provisions infrastructure declaratively and tracks its state, how Ansible configures servers and runs operations over SSH, and how Puppet's agents continuously enforce compliance and heal drift at scale. Along the way we'll touch on the real-world questions that matter — licensing changes, open-source forks, enterprise vs community editions, and tooling at scale. +> +> The punchline: these tools aren't competitors. They're complementary, each solving a different layer of the same problem. By the end you'll understand where each one fits — and how a typical production setup uses all three together: Terraform to provision the VM, Ansible to configure it and deploy the app, and Puppet to keep it compliant, forever. + ## 🌐 View the slides 👉 **https://ministicraft.pages.git.cloud.arnaud-pc.fr/finistdev-configuration-as-code/**