<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker-Compose on Martin Ahrer</title><link>https://www.martinahrer.at/tags/docker-compose/</link><description>Recent content in Docker-Compose on Martin Ahrer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 07 Feb 2017 00:00:00 +0000</lastBuildDate><atom:link href="https://www.martinahrer.at/tags/docker-compose/index.xml" rel="self" type="application/rss+xml"/><item><title>docker-compose scripting</title><link>https://www.martinahrer.at/2017/02/07/docker-compose-scripting/</link><pubDate>Tue, 07 Feb 2017 00:00:00 +0000</pubDate><guid>https://www.martinahrer.at/2017/02/07/docker-compose-scripting/</guid><description>&lt;div class="paragraph">
&lt;p>This time we look at managing large numbers of compose projects.&lt;/p>
&lt;/div>
&lt;div class="paragraph">
&lt;p>When building complex infrastructure using docker-compose we soon end in a mess of scripts for starting, updating, etc. containers.
I will try to describe an approach that has helped to get this done in a very structured way.&lt;/p>
&lt;/div></description></item><item><title>docker-compose modularization</title><link>https://www.martinahrer.at/2017/02/06/docker-compose-modularization/</link><pubDate>Mon, 06 Feb 2017 00:00:00 +0000</pubDate><guid>https://www.martinahrer.at/2017/02/06/docker-compose-modularization/</guid><description>&lt;div id="preamble">
&lt;div class="sectionbody">
&lt;div class="paragraph">
&lt;p>In this blog post we are looking into how we can create modular compose projects.&lt;/p>
&lt;/div>
&lt;div class="paragraph">
&lt;p>With &lt;code>docker-compose&lt;/code> we can describe a bunch of containers and container related resources such as networks and volumes that make up an application. All this is usually going into a &lt;code>docker-compose.yml&lt;/code> file.&lt;/p>
&lt;/div></description></item></channel></rss>