<?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>Monorepo on Pasi Dev</title><link>https://dev.pasi.pl/tags/monorepo/</link><description>Recent content in Monorepo on Pasi Dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 16 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://dev.pasi.pl/tags/monorepo/index.xml" rel="self" type="application/rss+xml"/><item><title>Simplified monorepo with docker compose for local development, CI and production</title><link>https://dev.pasi.pl/simplified-monorepo-with-docker-compose-for-local-development-ci-and-production/</link><pubDate>Tue, 16 Dec 2025 00:00:00 +0000</pubDate><guid>https://dev.pasi.pl/simplified-monorepo-with-docker-compose-for-local-development-ci-and-production/</guid><description>&lt;p&gt;Docker Compose is often treated as a &amp;ldquo;local-only&amp;rdquo; tool, while CI pipelines reimplement the same logic with custom scripts and duplicated image definitions. That duplication causes drift, surprises, and unnecessary complexity.&lt;/p&gt;
&lt;p&gt;Using &lt;strong&gt;multi-stage Dockerfiles&lt;/strong&gt; combined with &lt;strong&gt;build targets selected via environment variables&lt;/strong&gt;, Docker Compose can become the single source of truth for:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;local development&lt;/li&gt;
&lt;li&gt;production-like local testing&lt;/li&gt;
&lt;li&gt;CI build&lt;/li&gt;
&lt;li&gt;CI push&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;No separate compose files. No duplicated CI job definitions per image.&lt;/p&gt;</description></item></channel></rss>