<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on Yanis Gramitzky - Infrastructure &amp; Automation</title><link>https://ygramitzky.de/tags/infrastructure/</link><description>Recent content in Infrastructure on Yanis Gramitzky - Infrastructure &amp; Automation</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 19 Mar 2026 09:00:00 +0100</lastBuildDate><atom:link href="https://ygramitzky.de/tags/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker Compose Deep Dive: Every Option Explained</title><link>https://ygramitzky.de/posts/docker/docker_compose/</link><pubDate>Thu, 19 Mar 2026 09:00:00 +0100</pubDate><guid>https://ygramitzky.de/posts/docker/docker_compose/</guid><description>&lt;h2 id="what-is-docker-compose"&gt;What Is Docker Compose?&lt;/h2&gt;
&lt;p&gt;Docker Compose is a tool for defining and running &lt;strong&gt;multi-container applications&lt;/strong&gt;. Instead of typing long &lt;code&gt;docker run&lt;/code&gt; commands with dozens of flags, you describe your entire stack — services, networks, volumes, secrets — in a single YAML file. One command (&lt;code&gt;docker compose up&lt;/code&gt;) brings everything to life.&lt;/p&gt;
&lt;p&gt;Compose is the standard way to run local development environments, CI pipelines, and even lightweight production workloads. Understanding its full vocabulary gives you precise control over how your containers behave.&lt;/p&gt;</description></item></channel></rss>