Terraform + Ansible: The DevOps Workflow That Actually Works
Video write-up
Terraform vs Ansible is often the wrong debate. In this video, I’ll explain Infrastructure as Code, compare how Terraform/OpenTofu and Ansible actually work, and use my Proxmox HomeLab as one consistent example. We’ll look at where their responsibilities overlap, why OpenTofu manages my Proxmox VMs, why Ansible handles configuration and operational tasks on the Proxmox hosts, and when using both creates a cleaner workflow.
Up next
More videos with similar topics.
Manage your network like a PRO // Netbox Tutorial
In this video, I show you how to manage your network infrastructure like a pro using NetBox - the ultimate IP Address and Data Center Infrastructure Management platform. We'll start by deploying NetBox in Docker using my boilerplates tool,…
Manage Authentik Resources in Terraform
In this video, I show how to manage Authentik resources with Terraform, including provider setup, outposts, and applications. Prerequisites Set secure variables for AUTHENTIK_URL and AUTHENTIK_TOKEN (do not hardcode tokens). Terraform proj…
The BEST alternative to Docker and VMs! // Proxmox LXC
In this video, we're diving into Proxmox Linux Containers (LXC)! While Docker has been a popular choice, LXC offers a powerful and often overlooked alternative for creating isolated environments without the overhead of a full-blown operati…
Manage Checkmk IT monitoring in Ansible
In this video we will show you how to automate Checkmk using Ansible. We’ll cover installing and configuring Checkmk with Ansible, adding hosts and services automatically, and managing rules to tailor your monitoring setup. This tutorial p…
Let’s migrate from Terraform to OpenTofu!
In this video, I show you how to easily migrate from Terraform to OpenTofu, the exciting new open-source alternative to HashiCorp Terraform. We’ll explore the recent changes in Terraform's licensing and how they’ve influenced my decision t…
Better HomeLab Secret Management // Infisical Tutorial
HomeLab secrets usually start simple: one .env file next to a Docker Compose stack. But over time, those secrets spread into GitLab variables, deployment scripts, copied folders, backups, notes, and places where they should not live. In th…