<?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 *scratch*</title>
    <link>https://www.scrivano.org/tags/docker-compose/</link>
    <description>Recent content in Docker-Compose on *scratch*</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 06 Jun 2026 10:03:54 +0000</lastBuildDate>
    <atom:link href="https://www.scrivano.org/tags/docker-compose/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to deploy a WordPress Docker container using docker-compose</title>
      <link>https://www.scrivano.org/posts/2015-04-19-wordpress-in-a-docker-container/</link>
      <pubDate>Sun, 19 Apr 2015 23:25:49 +0000</pubDate>
      <guid>https://www.scrivano.org/posts/2015-04-19-wordpress-in-a-docker-container/</guid>
      <description>&lt;p&gt;These are the steps to setup the current website in a Docker container. The setup uses docker-compose to declaratively describe a two-container application: a MySQL 5.5 database and a WordPress frontend. Docker links tie them together so that the web container can reach the database by hostname, without needing to hard-code any IP addresses or manage networking manually. A single &lt;code&gt;docker-compose up&lt;/code&gt; command downloads the required images and starts both containers, with port 80 on the host forwarded into the WordPress container.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
