<?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>Docker-Compose on phinguin123</title>
    <link>http://phinguin.dev/tags/docker-compose/</link>
    <description>Recent content in Docker-Compose on phinguin123</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>2026 phinguin</copyright>
    <lastBuildDate>Thu, 05 Feb 2026 12:56:00 +0900</lastBuildDate>
    <atom:link href="http://phinguin.dev/tags/docker-compose/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Dev and Prod on One Server</title>
      <link>http://phinguin.dev/blog/dev-and-prod-on-one-server/</link>
      <pubDate>Thu, 05 Feb 2026 12:56:00 +0900</pubDate>
      <guid>http://phinguin.dev/blog/dev-and-prod-on-one-server/</guid>
      <description>Running dev and prod side by side on one AWS box. Compose project names fixed the collisions, and made it really easy to forget everything Docker doesn&amp;rsquo;t own.</description>
    </item>
    <item>
      <title>Dev, Staging, Prod on Two Oracle ARM Boxes</title>
      <link>http://phinguin.dev/blog/dev-prod-on-two-arm-servers/</link>
      <pubDate>Mon, 01 Dec 2025 11:08:00 +0900</pubDate>
      <guid>http://phinguin.dev/blog/dev-prod-on-two-arm-servers/</guid>
      <description>Setting up a native arm64 dev → staging → prod flow on Oracle&amp;rsquo;s free Ampere A1, with an x86 desktop and two identical servers.</description>
    </item>
  </channel>
</rss>
