<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps on David Cajio</title><link>https://davidcajio.com/tags/devops/</link><description>Recent content in DevOps on David Cajio</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 David Cajio</copyright><lastBuildDate>Thu, 18 Jun 2026 13:00:00 -0400</lastBuildDate><atom:link href="https://davidcajio.com/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Inside My Arch + Hyprland Setup: Building a Fully Reproducible Desktop Environment</title><link>https://davidcajio.com/posts/arch-hyprland-reproducible-desktop-environment/</link><pubDate>Thu, 18 Jun 2026 13:00:00 -0400</pubDate><guid>https://davidcajio.com/posts/arch-hyprland-reproducible-desktop-environment/</guid><description>How I built a reproducible Arch Linux and Hyprland desktop environment with modular config files, wallpaper-driven theming, Waybar, Ghostty, multi-monitor support, and machine-specific dotfile templating.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://davidcajio.com/posts/arch-hyprland-reproducible-desktop-environment/feature.jpg"/></item><item><title>Managing Dotfiles with ChezMoi: A Fully Automated Infrastructure-as-Code Desktop for Arch Linux and Hyprland</title><link>https://davidcajio.com/posts/chezmoi-dotfiles-arch-linux-hyprland-automation/</link><pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate><guid>https://davidcajio.com/posts/chezmoi-dotfiles-arch-linux-hyprland-automation/</guid><description>&lt;p&gt;I’ve landed on a fairly opinionated conclusion over the years: dotfiles management only works when it disappears into your workflow. The moment I have to “think about syncing configs,” I stop maintaining it.&lt;/p&gt;
&lt;p&gt;That’s why I eventually standardized on chezmoi backed by a plain Git repository, with a fully automated apply model across my Arch + Hyprland environment.&lt;/p&gt;
&lt;p&gt;This isn’t a “nice dotfiles setup.” It’s a repeatable machine bootstrap system.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://davidcajio.com/posts/chezmoi-dotfiles-arch-linux-hyprland-automation/feature.jpg"/></item><item><title>Building a Second Brain for AWS Certification with Obsidian and AI</title><link>https://davidcajio.com/posts/aws-second-brain-obsidian-ai-workflow/</link><pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate><guid>https://davidcajio.com/posts/aws-second-brain-obsidian-ai-workflow/</guid><description>&lt;p&gt;When I started seriously preparing for AWS certifications, I hit a familiar problem for anyone working in infrastructure: the volume of information isn’t the hard part — retention and structure are.&lt;/p&gt;
&lt;p&gt;You can watch hours of training, build labs, and take pages of notes, but unless that information is continuously refined, it decays quickly. A few weeks later, the details blur: IAM evaluation logic, VPC routing behavior, the subtle differences between endpoint types — all of it starts to fade.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://davidcajio.com/posts/aws-second-brain-obsidian-ai-workflow/feature.jpg"/></item><item><title>Practical Multi-Region E-Commerce Architecture on AWS (Without Overengineering It)</title><link>https://davidcajio.com/posts/aws-multi-region-ecommerce-architecture-practical-guide/</link><pubDate>Mon, 01 Jun 2026 13:46:15 -0400</pubDate><guid>https://davidcajio.com/posts/aws-multi-region-ecommerce-architecture-practical-guide/</guid><description>&lt;p&gt;When most people talk about multi-region architectures, they immediately jump to diagrams full of globally distributed databases, active-active replication, service meshes, and enough complexity to require a dedicated platform team.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s not the reality for most e-commerce companies.&lt;/p&gt;
&lt;p&gt;At Rough Country, my responsibility is managing the infrastructure that powers our online storefronts while also leading development efforts, reviewing code, managing deployments, and supporting multiple business initiatives. Every architectural decision has to balance reliability, performance, operational complexity, and cost.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://davidcajio.com/posts/aws-multi-region-ecommerce-architecture-practical-guide/feature.jpg"/></item></channel></rss>