<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>DevOps - Tag - Simi Studio</title>
        <link>/en/tags/devops/</link>
        <description>DevOps - Tag - Simi Studio</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>simi@simi.studio (Simi)</managingEditor>
            <webMaster>simi@simi.studio (Simi)</webMaster><lastBuildDate>Sat, 28 Mar 2026 10:00:00 &#43;0800</lastBuildDate><atom:link href="/en/tags/devops/" rel="self" type="application/rss+xml" /><item>
    <title>Docker Best Practices</title>
    <link>/en/posts/docker-best-practices/</link>
    <pubDate>Sat, 28 Mar 2026 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/en/posts/docker-best-practices/</guid>
    <description><![CDATA[Docker containerization coding conventions and best practices covering Docker 29.4, nftables, containerd image store, multi-platform images, security scanning, and more]]></description>
</item>
<item>
    <title>Docker Compose Best Practices</title>
    <link>/en/posts/docker-compose-best-practices-v2/</link>
    <pubDate>Sat, 28 Mar 2026 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/en/posts/docker-compose-best-practices-v2/</guid>
    <description><![CDATA[<p><a href="https://docs.docker.com/compose/" target="_blank" rel="noopener noreffer ">Docker Compose</a> does one thing well: it describes a multi-container environment and lets you spin it up consistently everywhere—your laptop, a CI runner, a colleague&rsquo;s machine.</p>]]></description>
</item>
<item>
    <title>Docker Compose Best Practices</title>
    <link>/en/posts/docker-compose-best-practices/</link>
    <pubDate>Sat, 28 Mar 2026 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/en/posts/docker-compose-best-practices/</guid>
    <description><![CDATA[<p>Docker Compose is excellent at one thing: describing a small multi-container environment that developers and CI can start consistently. That is why it works so well for local stacks, integration tests, and disposable support tooling.</p>]]></description>
</item>
<item>
    <title>Git Workflows 2025: Trunk-Based Development Is the Answer</title>
    <link>/en/posts/git-workflows-2025/</link>
    <pubDate>Mon, 22 Dec 2025 20:06:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/en/posts/git-workflows-2025/</guid>
    <description><![CDATA[GitFlow is dead, Trunk-Based Development is the right approach for modern dev teams. This article explains migration strategy.]]></description>
</item>
<item>
    <title>Kubernetes Production Best Practices: 2025 Updated</title>
    <link>/en/posts/kubernetes-production-best-practices/</link>
    <pubDate>Fri, 19 Dec 2025 15:07:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/en/posts/kubernetes-production-best-practices/</guid>
    <description><![CDATA[Kubernetes 1.28+ production config checklist: resource limits, health checks, rolling updates, security settings.]]></description>
</item>
<item>
    <title>Docker Security Hardening: Production Checklist</title>
    <link>/en/posts/docker-security-hardening/</link>
    <pubDate>Fri, 15 Aug 2025 10:00:00 &#43;0800</pubDate>
    <author>simi@simi.studio (Simi)</author>
    <guid>/en/posts/docker-security-hardening/</guid>
    <description><![CDATA[Most Docker security incidents aren't 0days—they're misconfigurations. This article covers production Docker security configuration in practical checklists. Theory-free.]]></description>
</item>
</channel>
</rss>
