Skills Matrix on Suzf Blog

Terraform Multi-Cloud Best Practices

i@suzf.net (JeffreySu) — Tue, 31 Mar 2026 22:54:13 +0800

When infrastructure spans AWS, GCP, and Azure, Terraform’s management complexity increases dramatically. This post summarizes practical experience in organizing code, managing Providers, and unifying workflows in multi-cloud scenarios.

OpenClaw Must-Have Skills — Highly Recommended

i@suzf.net (JeffreySu) — Tue, 31 Mar 2026 22:41:40 +0800

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.

OpenClaw Step-by-Step Installation Guide

i@suzf.net (JeffreySu) — Tue, 31 Mar 2026 22:37:32 +0800

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.

Dockerfile Pitfalls Guide

i@suzf.net (JeffreySu) — Tue, 31 Mar 2026 22:23:03 +0800

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.

Dockerfile Best Practices

i@suzf.net (JeffreySu) — Tue, 31 Mar 2026 22:20:51 +0800

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.

Terraform State Management & Team Collaboration Best Practices

i@suzf.net (JeffreySu) — Tue, 31 Mar 2026 22:17:52 +0800

Terraform’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.

This post summarizes State management best practices, covering remote backend configuration, state locking, workspace isolation, and daily operational tips.

nomad server cluster upgrade

i@suzf.net (JeffreySu) — Tue, 31 Mar 2026 22:09:08 +0800

Upgrading a Nomad Server cluster follows the core principle of “backup first, rolling upgrade, Followers before Leader”. Since Nomad relies on the Raft consensus protocol, Quorum must be maintained throughout the upgrade process, otherwise the cluster becomes unavailable.

Here is the detailed upgrade procedure:

consul server upgrade

i@suzf.net (JeffreySu) — Fri, 30 Jan 2026 16:32:53 +0800

Upgrading a Consul cluster must follow the principle of “step by step, Servers before Clients, maintain compatibility”. 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.

Below is a detailed upgrade roadmap and procedure: