<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Docker on sugar, spice, &amp;terminal? nice</title>
    <link>https://terminal.space/tag/docker/</link>
    <description>Recent content in Docker on sugar, spice, &amp;terminal? nice</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 09 Dec 2024 14:57:12 +0000</lastBuildDate>
    <atom:link href="https://terminal.space/tag/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Backing up docker volumes</title>
      <link>https://terminal.space/tech/backing-up-docker-volumes/</link>
      <pubDate>Mon, 09 Dec 2024 14:57:12 +0000</pubDate>
      <guid>https://terminal.space/tech/backing-up-docker-volumes/</guid>
      <description>&lt;p&gt;In today&amp;rsquo;s I-can&amp;rsquo;t-believe-I&amp;rsquo;m-doing-this-in-2024&lt;/p&gt;&#xA;&lt;p&gt;I needed to re-build my webserver because it kept hard-freezing every week (another post for another day). Since I use a docker setup for this, my setup is pretty turnkey - I just needed to copy over my docker volumes from the old host to the new host.&lt;/p&gt;&#xA;&lt;p&gt;That turned out to be a lot more annoying than what I wanted. See, this functionality hasn&amp;rsquo;t existed for a long time. You had to use some DIY &lt;a href=&#34;https://stackoverflow.com/questions/38298645/how-should-i-backup-restore-docker-named-volumes&#34;&gt;StackOverflow&lt;/a&gt; scripts. Apparently, this functionality is now built into Docker Desktop, but A. I&amp;rsquo;m ssh&amp;rsquo;d into a server and B. Docker Desktop is the trojan horse where they extort people for licenses. In either case, I just have access to the docker daemon.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Matching socks: Nginx &#43; php = Wordpress (Part 3)</title>
      <link>https://terminal.space/tech/matching-socks-nginx-php-wordpress-part-3/</link>
      <pubDate>Wed, 02 Jun 2021 11:01:09 +0000</pubDate>
      <guid>https://terminal.space/tech/matching-socks-nginx-php-wordpress-part-3/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://terminal.space/tech/matching-socks-nginx-php-wordpress-part-3/images/alfred-rowe-1zTetyivDYE-unsplash.jpg&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;&lt;a href=&#34;https://terminal.space/tech/wordpress-hosting-docker-style-part-1/&#34;&gt;Part 1: Wordpress hosting, docker style&lt;/a&gt;&lt;br&gt;&#xA;&lt;a href=&#34;https://terminal.space/tech/cron-letsencrypt-docker-style-part-2/&#34;&gt;Part 2: Cron + LetsEncrypt, docker style&lt;/a&gt;&lt;br&gt;&#xA;&lt;a href=&#34;https://terminal.space/tech/matching-socks-nginx-php-wordpress-part-3/&#34;&gt;Part 3: Matching socks: Nginx + php = Wordpress&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Previously, we&amp;rsquo;ve covered terminating SSL connections and running cron jobs. Now it&amp;rsquo;s time to actually set up a wordpress installation. The two main ingredients are a web server, and a php server. All requests go through the web server (nginx, again in this case). If the filepath ends in a .php extension, then the request gets forwarded to the php-fpm (basically php with a &lt;a href=&#34;https://stackoverflow.com/a/2089297/3029173&#34;&gt;FastCGI&lt;/a&gt; implementation) to do the server-side processing.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cron &#43; LetsEncrypt, docker style (Part 2)</title>
      <link>https://terminal.space/tech/cron-letsencrypt-docker-style-part-2/</link>
      <pubDate>Mon, 15 Mar 2021 20:49:50 +0000</pubDate>
      <guid>https://terminal.space/tech/cron-letsencrypt-docker-style-part-2/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://terminal.space/tech/cron-letsencrypt-docker-style-part-2/images/glenn-carstens-peters-piNf3C4TViA-unsplash.jpg&#34;&#xA;    alt=&#34;Cornfield&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;p&gt;Cornfield&lt;/p&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;&lt;a href=&#34;https://terminal.space/tech/wordpress-hosting-docker-style-part-1/&#34;&gt;Part 1: Wordpress hosting, docker style&lt;/a&gt;&lt;br&gt;&#xA;&lt;a href=&#34;https://terminal.space/tech/cron-letsencrypt-docker-style-part-2/&#34;&gt;Part 2: Cron + LetsEncrypt, docker style&lt;/a&gt;&lt;br&gt;&#xA;&lt;a href=&#34;https://terminal.space/tech/matching-socks-nginx-php-wordpress-part-3/&#34;&gt;Part 3: Matching socks: Nginx + php = Wordpress&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Today, I&amp;rsquo;m going to talk about running background jobs with docker. On a non-docker system, you can set up a server to do many things at once - for example run nginx AND update your SSL certs periodically. However, with Docker, you have to choose. You either need to run each process as a separate docker container, or you need to use some sort of supervisor process (supervisord, &lt;a href=&#34;https://laptrinhx.com/docker-containers-running-alpine-linux-and-s6-for-process-management-solid-reliable-containers-3512281510/&#34;&gt;s6&lt;/a&gt;, systemd, etc) which will in-turn kick off the other processes you&amp;rsquo;re interested in.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Wordpress hosting, docker style (Part 1)</title>
      <link>https://terminal.space/tech/wordpress-hosting-docker-style-part-1/</link>
      <pubDate>Tue, 09 Mar 2021 07:07:32 +0000</pubDate>
      <guid>https://terminal.space/tech/wordpress-hosting-docker-style-part-1/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://terminal.space/tech/wordpress-hosting-docker-style-part-1/images/beanca-du-toit-pCNiuZ8lvpc-unsplash.jpg&#34;&#xA;    alt=&#34;A whale, coming out of the water&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;p&gt;A whale, coming out of the water&lt;/p&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;&lt;a href=&#34;https://terminal.space/tech/wordpress-hosting-docker-style-part-1/&#34;&gt;Part 1: Wordpress hosting, docker style&lt;/a&gt;&lt;br&gt;&#xA;&lt;a href=&#34;https://terminal.space/tech/cron-letsencrypt-docker-style-part-2/&#34;&gt;Part 2: Cron + LetsEncrypt, docker style&lt;/a&gt;&lt;br&gt;&#xA;&lt;a href=&#34;https://terminal.space/tech/matching-socks-nginx-php-wordpress-part-3/&#34;&gt;Part 3: Matching socks: Nginx + php = Wordpress&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Those &lt;a href=&#34;https://terminal.space/tech/wordpress-hosting-from-scratch/&#34;&gt;segfaults&lt;/a&gt; I mentioned? Yeah, they proved unsolvable. Nginx Unit seems to be having a rough time and un-extracting Nginx Unit from the install script was more difficult than expected too.&lt;/p&gt;&#xA;&lt;p&gt;Instead, I spent more time than that setting up my &lt;a href=&#34;https://github.com/AnilRedshift/www_docker/&#34;&gt;own cluster of docker containers&lt;/a&gt;. The benefit is that I can now run a whole copy locally, test changes, and then push to production. It also allows me to track what changes to all the various .conf files I&amp;rsquo;ve been making. Today, I&amp;rsquo;ll talk about setting up a SSL-terminating reverse-proxy, and how to host it with docker-compose.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
