<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Suzf Blog</title>
        <link>https://suzf.net/blog/</link>
        <description>Suzf&#39;s Blog</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>i@suzf.net (JeffreySu)</managingEditor>
            <webMaster>i@suzf.net (JeffreySu)</webMaster><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 31 Mar 2026 22:54:13 &#43;0800</lastBuildDate>
            <atom:link href="https://suzf.net/blog/index.xml" rel="self" type="application/rss+xml" />
        <item>
    <title>Terraform Multi-Cloud Best Practices</title>
    <link>https://suzf.net/blog/posts/terraform-multi-cloud-best-practices/</link>
    <pubDate>Tue, 31 Mar 2026 22:54:13 &#43;0800</pubDate>
    <author>i@suzf.net (JeffreySu)</author>
    <guid>https://suzf.net/blog/posts/terraform-multi-cloud-best-practices/</guid>
    <description><![CDATA[<p>When infrastructure spans AWS, GCP, and Azure, Terraform&rsquo;s management complexity increases dramatically. This post summarizes practical experience in organizing code, managing Providers, and unifying workflows in multi-cloud scenarios.</p>]]></description>
</item>
<item>
    <title>OpenClaw Must-Have Skills — Highly Recommended</title>
    <link>https://suzf.net/blog/posts/openclaw-must-have-skills/</link>
    <pubDate>Tue, 31 Mar 2026 22:41:40 &#43;0800</pubDate>
    <author>i@suzf.net (JeffreySu)</author>
    <guid>https://suzf.net/blog/posts/openclaw-must-have-skills/</guid>
    <description><![CDATA[<p>The OpenClaw Skills ecosystem (ClawHub) has surpassed 13,000 skill packages, but quality varies wildly. A February 2026 security audit flagged ~13.4% for critical issues. This post recommends genuinely useful Skills by use case, helping you avoid the minefield.</p>]]></description>
</item>
<item>
    <title>OpenClaw Step-by-Step Installation Guide</title>
    <link>https://suzf.net/blog/posts/openclaw-install-guide/</link>
    <pubDate>Tue, 31 Mar 2026 22:37:32 &#43;0800</pubDate>
    <author>i@suzf.net (JeffreySu)</author>
    <guid>https://suzf.net/blog/posts/openclaw-install-guide/</guid>
    <description><![CDATA[<p>OpenClaw is an open-source, self-hosted AI assistant platform (formerly Clawdbot / Moltbot) that supports both cloud and local models. This guide walks you through installation, configuration, and your first run from scratch.</p>]]></description>
</item>
<item>
    <title>Dockerfile Pitfalls Guide</title>
    <link>https://suzf.net/blog/posts/dockerfile-pitfalls-guide/</link>
    <pubDate>Tue, 31 Mar 2026 22:23:03 &#43;0800</pubDate>
    <author>i@suzf.net (JeffreySu)</author>
    <guid>https://suzf.net/blog/posts/dockerfile-pitfalls-guide/</guid>
    <description><![CDATA[<p>Writing a Dockerfile seems simple, but production environments are full of hidden traps. This post covers common Dockerfile pitfalls and their solutions to help you avoid painful debugging sessions.</p>]]></description>
</item>
<item>
    <title>Dockerfile Best Practices</title>
    <link>https://suzf.net/blog/posts/dockerfile-best-practices/</link>
    <pubDate>Tue, 31 Mar 2026 22:20:51 &#43;0800</pubDate>
    <author>i@suzf.net (JeffreySu)</author>
    <guid>https://suzf.net/blog/posts/dockerfile-best-practices/</guid>
    <description><![CDATA[<p>A well-written Dockerfile can significantly reduce image size, speed up builds, and improve security. This post summarizes the most practical Dockerfile conventions for daily work.</p>]]></description>
</item>
<item>
    <title>Terraform State Management &amp; Team Collaboration Best Practices</title>
    <link>https://suzf.net/blog/posts/terraform-state-management-best-practices/</link>
    <pubDate>Tue, 31 Mar 2026 22:17:52 &#43;0800</pubDate>
    <author>i@suzf.net (JeffreySu)</author>
    <guid>https://suzf.net/blog/posts/terraform-state-management-best-practices/</guid>
    <description><![CDATA[<p>Terraform&rsquo;s State file is the core of infrastructure as code — it records the mapping between real resources and your configuration. Poor State management in a team setting can lead to resource drift, lock conflicts, or even accidental infrastructure destruction.</p>
<p>This post summarizes State management best practices, covering remote backend configuration, state locking, workspace isolation, and daily operational tips.</p>]]></description>
</item>
<item>
    <title>nomad server cluster upgrade</title>
    <link>https://suzf.net/blog/posts/nomad-server-cluster-upgrade/</link>
    <pubDate>Tue, 31 Mar 2026 22:09:08 &#43;0800</pubDate>
    <author>i@suzf.net (JeffreySu)</author>
    <guid>https://suzf.net/blog/posts/nomad-server-cluster-upgrade/</guid>
    <description><![CDATA[<p>Upgrading a Nomad Server cluster follows the core principle of &ldquo;backup first, rolling upgrade, Followers before Leader&rdquo;. Since Nomad relies on the Raft consensus protocol, Quorum must be maintained throughout the upgrade process, otherwise the cluster becomes unavailable.</p>
<p>Here is the detailed upgrade procedure:</p>]]></description>
</item>
<item>
    <title>consul server upgrade</title>
    <link>https://suzf.net/blog/posts/consul-server-upgrade/</link>
    <pubDate>Fri, 30 Jan 2026 16:32:53 &#43;0800</pubDate>
    <author>i@suzf.net (JeffreySu)</author>
    <guid>https://suzf.net/blog/posts/consul-server-upgrade/</guid>
    <description><![CDATA[<p>Upgrading a Consul cluster must follow the principle of &ldquo;step by step, Servers before Clients, maintain compatibility&rdquo;. If the version gap is too large (e.g., jumping from 1.1x directly to 1.2x), a direct upgrade may cause Raft protocol incompatibility or data corruption.</p>
<p>Below is a detailed upgrade roadmap and procedure:</p>]]></description>
</item>
</channel>
</rss>
