# 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/**

## 🛠️ Built with

- [Reveal.js](https://revealjs.com/) — HTML presentation framework

## 📦 Deployment

Slides are automatically published via [git-pages](https://codeberg.org/git-pages/git-pages) on every push to the `pages` branch.