<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>DevOps on nuteo</title>
    <link>https://www.nuteo.info/tags/devops/</link>
    <description>Recent content in DevOps on nuteo</description>
    <generator>Hugo</generator>
    <language></language>
    <lastBuildDate>Thu, 05 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.nuteo.info/tags/devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Dev Infrastructure Setup</title>
      <link>https://www.nuteo.info/work/dev-infra/</link>
      <pubDate>Tue, 15 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://www.nuteo.info/work/dev-infra/</guid>
      <description>Self-hosted development infrastructure on Ubuntu with Docker, Next.js, and AI tooling</description>
    </item>
    <item>
      <title>ตั้งค่า Dev Infrastructure สำหรับ Self-Hosted AI</title>
      <link>https://www.nuteo.info/th/work/dev-infra/</link>
      <pubDate>Tue, 15 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://www.nuteo.info/th/work/dev-infra/</guid>
      <description>Self-hosted development environment บน Ubuntu พร้อม Docker, Next.js, และ AI tooling</description>
    </item>
    <item>
      <title>开发基础设施设置</title>
      <link>https://www.nuteo.info/zh/work/dev-infra/</link>
      <pubDate>Tue, 15 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://www.nuteo.info/zh/work/dev-infra/</guid>
      <description>Ubuntu 上的自托管开发环境，配备 Docker、Next.js 和 AI 工具</description>
    </item>
    <item>
      <title>Docker Compose Patterns That Actually Scale</title>
      <link>https://www.nuteo.info/work/docker-compose-patterns/</link>
      <pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://www.nuteo.info/work/docker-compose-patterns/</guid>
      <description>&lt;p&gt;Docker Compose is the tool everyone recommends and nobody does correctly. You start with three services in a YAML file. Six months later you have thirty, and your docker-compose.yml is a file that nobody fully understands but everybody fears touching.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve been through this pattern enough times that I&amp;rsquo;ve developed a structure that actually holds up as projects grow. What follows isn&amp;rsquo;t official Docker guidance — it&amp;rsquo;s the lessons I learned from breaking things repeatedly.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Docker Compose Patterns ที่ขยายได้จริง</title>
      <link>https://www.nuteo.info/th/work/docker-compose-patterns/</link>
      <pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://www.nuteo.info/th/work/docker-compose-patterns/</guid>
      <description>วิธีจัด Docker Compose สำหรับโปรเจกต์ที่เติบโต — จาก dev คนเดียวไปสู่ multi-service production</description>
    </item>
    <item>
      <title>Docker Compose Patterns 实际可扩展</title>
      <link>https://www.nuteo.info/zh/work/docker-compose-patterns/</link>
      <pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://www.nuteo.info/zh/work/docker-compose-patterns/</guid>
      <description>如何为成长型项目构建 Docker Compose — 从单人开发到多服务生产环境</description>
    </item>
  </channel>
</rss>
