<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Automation on Panic! At The Terminal</title>
    <link>https://blog.nousiainen.xyz/categories/automation/</link>
    <description>Recent content in Automation on Panic! At The Terminal</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 09 Sep 2025 21:04:56 +0300</lastBuildDate>
    <atom:link href="https://blog.nousiainen.xyz/categories/automation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Docker Instance Upgrades with Ansible</title>
      <link>https://blog.nousiainen.xyz/docs/docker-upgrades/</link>
      <pubDate>Wed, 16 Jul 2025 18:23:20 +0200</pubDate>
      <guid>https://blog.nousiainen.xyz/docs/docker-upgrades/</guid>
      <description>&lt;h1 id=&#34;docker-instance-upgrades-with-ansible&#34;&gt;&#xA;  Docker Instance Upgrades with Ansible&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#docker-instance-upgrades-with-ansible&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;This guide shows how to automate Docker container upgrades using Ansible playbooks instead of manual updates. By automating this process, you ensure consistency, reduce errors, and save time when updating multiple Docker instances across your infrastructure.&lt;/p&gt;&#xA;&lt;h2 id=&#34;infrastructure-overview&#34;&gt;&#xA;  Infrastructure Overview&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#infrastructure-overview&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;My homelab includes these Docker-based services:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Nginx Proxy Manager&lt;/strong&gt; (proxy.home.arpa) - Reverse proxy with SSL&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Healthchecks&lt;/strong&gt; (health.home.arpa) - Monitoring service&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Home Assistant&lt;/strong&gt; (hass.home.arpa) - Home automation platform&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Bitwarden&lt;/strong&gt; (bit.home.arpa) - Password manager&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;ansible-playbook-structure&#34;&gt;&#xA;  Ansible Playbook Structure&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#ansible-playbook-structure&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;h3 id=&#34;host-configuration&#34;&gt;&#xA;  Host Configuration&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#host-configuration&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h3&gt;&#xA;&lt;p&gt;The playbook targets specific hosts with Docker services:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Automating KVM Backups with Ansible</title>
      <link>https://blog.nousiainen.xyz/docs/backing-up-kvm/</link>
      <pubDate>Sat, 12 Jul 2025 10:00:00 +0300</pubDate>
      <guid>https://blog.nousiainen.xyz/docs/backing-up-kvm/</guid>
      <description>&lt;h1 id=&#34;automating-kvm-homelab-backups-with-ansible&#34;&gt;&#xA;  Automating KVM Homelab Backups with Ansible&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#automating-kvm-homelab-backups-with-ansible&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;When you&amp;rsquo;re running a dozen virtual machines in your homelab, manual backups quickly become a nightmare.&lt;/p&gt;&#xA;&lt;p&gt;In this post, I&amp;rsquo;ll walk you through my Ansible-based backup strategy for my KVM homelab. It automatically backs up all VMs by shutting them down gracefully, copying their disk images and configurations to a NAS, and bringing them back online.&lt;/p&gt;&#xA;&lt;h2 id=&#34;backup-strategy&#34;&gt;&#xA;  Backup Strategy&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#backup-strategy&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;My backup strategy uses Ansible to orchestrate the entire process:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
