<?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 donisewell.com</title>
		<link>https://blog.donisewell.com/tags/docker/</link>
		<description>Recent content in Docker on donisewell.com</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 05 Sep 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://blog.donisewell.com/tags/docker/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>My Automated Pipeline for Blogging From Obsidian</title>
				<link>https://blog.donisewell.com/blog/my-automated-pipeline-for-blogging-from-obsidian/</link>
				<pubDate>Sat, 05 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://blog.donisewell.com/blog/my-automated-pipeline-for-blogging-from-obsidian/</guid>
				<description>&lt;h1 id=&#34;overview&#34;&gt;Overview&lt;/h1&gt;&#xA;&lt;p&gt;I set out to make my workflow for posting here as frictionless as possible which means as automated as possible. Anyone who&amp;rsquo;s spoken to me in a work context for more than five minutes knows my knowledge work revolves around Obsidian so it&amp;rsquo;s a natural starting point for this workflow.&lt;/p&gt;&#xA;&lt;p&gt;My home lab already makes heavy use of Docker so fitting this all within that architecture also makes this more familiar and  maintainable in the long run. I&amp;rsquo;ve already got backup and maintenance scripts running for the existing containers so adding a few more doesn&amp;rsquo;t add any more O&amp;amp;M overhead.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
