<?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 Melih Savdert&#39;s Tech Blog</title>
    <link>https://msavdert.github.io/categories/devops/</link>
    <description>Recent content in DevOps on Melih Savdert&#39;s Tech Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Melih Savdert</copyright>
    <lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://msavdert.github.io/categories/devops/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Building the Ultimate &#39;No-Sudo&#39; Modern Dotfiles: A Native &amp; Secure Approach</title>
      <link>https://msavdert.github.io/posts/no-sudo-modern-dotfiles/</link>
      <pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://msavdert.github.io/posts/no-sudo-modern-dotfiles/</guid>
      <description>&lt;p&gt;Managing my developer environment across multiple machines (macOS, Ubuntu, Oracle Linux, and minimal Docker containers) has always been a challenge. Most dotfiles setups I&amp;rsquo;ve seen rely on brittle helper scripts, global &lt;code&gt;sudo&lt;/code&gt; installations, or manual token handling.&lt;/p&gt;&#xA;&lt;p&gt;I decided to fix this by building a &lt;strong&gt;fully native, no-sudo, and secure&lt;/strong&gt; dotfiles infrastructure from the ground up. Here’s how I modernized my workflow and why it’s a game-changer for my daily productivity.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
