<?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 Kizito</title>
		<link>https://kizi.to/tags/docker/</link>
		<description>Recent content in docker on Kizito</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 21 Aug 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://kizi.to/tags/docker/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>prod like a pro</title>
				<link>https://kizi.to/prod-like-a-pro/</link>
				<pubDate>Fri, 21 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://kizi.to/prod-like-a-pro/</guid>
				<description>&lt;p&gt;since starting to release/deploy some of my personal projects to the wild, i&amp;rsquo;ve always fancied getting close to a release pipeline which is as seamless and &amp;ldquo;intuitive&amp;rdquo; as what i&amp;rsquo;ve grown accustomed to at work over the years.&lt;/p&gt;&#xA;&lt;p&gt;tl;dr?&lt;/p&gt;&#xA;&lt;p&gt;i deploy docker containers to cheap VPSes running &lt;a href=&#34;https://caprover.com/&#34;&gt;caprover&lt;/a&gt; using github actions and tagged releases.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-pro-looks-like&#34;&gt;what &amp;ldquo;pro&amp;rdquo; looks like&lt;/h2&gt;&#xA;&lt;p&gt;if you&amp;rsquo;ve worked in a place which has a functioning &amp;ldquo;devops&amp;rdquo; (or is it &amp;ldquo;devsecops&amp;rdquo; these days?), taking things to prod may look something like the following:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
