<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Ansible - Tag - log - Nicholas Ward</title><link>https://log.nicholas.uuard.com/tags/ansible/</link><description>Ansible - Tag - log - Nicholas Ward</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>nicholaspward@outlook.com (Nicholas Ward)</managingEditor><webMaster>nicholaspward@outlook.com (Nicholas Ward)</webMaster><lastBuildDate>Tue, 07 Jul 2026 10:00:00 -0500</lastBuildDate><atom:link href="https://log.nicholas.uuard.com/tags/ansible/" rel="self" type="application/rss+xml"/><item><title>🏗️ Home Ops Upgrades</title><link>https://log.nicholas.uuard.com/posts/2026-07-07-home-ops/</link><pubDate>Tue, 07 Jul 2026 10:00:00 -0500</pubDate><author>nicholas</author><guid>https://log.nicholas.uuard.com/posts/2026-07-07-home-ops/</guid><description><![CDATA[<p>As the number of self-hosted services I use regularly has grown, managing them by hand began to feel wrong, and occasionally annoying and tedious. It ends now!</p>






<figure>
  <a
    class="lightgallery"
    href="https://files.web-log.uuard.com/2026-07-07-home-ops/images/portainer-container-dashboard.png"
    data-thumbnail="https://files.web-log.uuard.com/2026-07-07-home-ops/images/portainer-container-dashboard.png"
    data-sub-html="Container dashboard - many apps">
    
  </a>

  
    <figcaption>Container dashboard - many apps</figcaption>
  
</figure>

<p>In the beginning, my workflow was pretty sloppy since much of the deployment/management depended on me remembering to restart a container or update a version, manually copy a secret here and there. Things like this. Totally maintainable, sustainable with some effort, but it is not <em>the way</em>. And to some degree these manual interventions will always be necessary, but it will serve me well to reduce them and automate them away as much as reasonable to help these apps live far into the future with little fuss. Many of these apps have proven their usefulness to me over many years, so I have begun to take their management more seriously, slowly taking steps toward git-ops patterns and best practices. Before: scattered <code>.env</code> files. Flat directory of compose files. No documentation. Manually copying secrets by hand. Manually rebuilding host dependencies by hand. Now: a single command issued by a single click of a button (maybe I am overstating the simplicity here&hellip;nevertheless) will handle mostly everything I care about. Host setup, Compose projects, rendered secrets, state directories, validation, and deployment are all described in one place. Easy!</p>]]></description></item></channel></rss>