<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Yaml on JsonKit Blog</title>
    <link>https://jsokit.com/blog/tags/yaml/</link>
    <description>Recent content in Yaml on JsonKit Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© 2025 JsonKit</copyright>
    <lastBuildDate>Mon, 09 Feb 2026 19:15:54 +0000</lastBuildDate>
    <atom:link href="https://jsokit.com/blog/tags/yaml/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building Docker Compose Configs from Scratch: Engineering Practices for Service Orchestration</title>
      <link>https://jsokit.com/blog/posts/building-docker-compose-configs-from-scratch-engineering-practices-for-service-orchestration/</link>
      <pubDate>Mon, 09 Feb 2026 19:15:54 +0000</pubDate>
      <guid>https://jsokit.com/blog/posts/building-docker-compose-configs-from-scratch-engineering-practices-for-service-orchestration/</guid>
      <description>Building Docker Compose Configs from Scratch: Engineering Practices for Service Orchestration Recently deployed a full-stack project requiring Nginx + Node.js + MySQL + Redis working together. Hand-writing docker-compose.yml revealed how easy it is to mess up port mappings, volume mounts, environment variables, and service dependencies. So I built a generator and revisited Docker Compose core concepts.&#xA;Core Technology of YAML Generation Docker Compose configuration is essentially YAML-formatted service orchestration. The core data structure:</description>
    </item>
  </channel>
</rss>
