<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Application Deployment on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/application-deployment/</link><description>Recent content in Application Deployment on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 25 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/application-deployment/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 7: Composing Multi-Container Applications</title><link>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/07-compose-applications/</link><pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/07-compose-applications/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 7! So far, you&amp;rsquo;ve mastered the art of running individual Linux containers on your Mac using Apple&amp;rsquo;s powerful &lt;code&gt;container&lt;/code&gt; CLI. You&amp;rsquo;ve built images, run single services, and even understood the fundamental architecture that makes it all possible. That&amp;rsquo;s fantastic!&lt;/p&gt;
&lt;p&gt;But what happens when your application isn&amp;rsquo;t just one simple service? Most modern applications are a collection of interconnected services: a web front-end, a backend API, a database, a caching layer, and perhaps more. Managing each of these as separate &lt;code&gt;container run&lt;/code&gt; commands can quickly become a tangled mess. This is where the concept of &amp;ldquo;composing&amp;rdquo; multi-container applications comes into play.&lt;/p&gt;</description></item></channel></rss>