<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deployment on My Blog</title><link>https://blog.uptick.be/tags/deployment/</link><description>Recent content in Deployment on My Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 04 Nov 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://blog.uptick.be/tags/deployment/index.xml" rel="self" type="application/rss+xml"/><item><title>How this blog is built, checked and deployed</title><link>https://blog.uptick.be/posts/how-this-blog-is-built/</link><pubDate>Wed, 04 Nov 2026 09:00:00 +0000</pubDate><guid>https://blog.uptick.be/posts/how-this-blog-is-built/</guid><description>&lt;p&gt;This blog is a pile of Markdown files, a tiny theme and a handful of shell scripts. Publishing a post means pushing to &lt;code&gt;main&lt;/code&gt;. About a minute later it is live. This is how the pieces fit together, and what went wrong on the way.&lt;/p&gt;</description></item><item><title>Rolling back safely</title><link>https://blog.uptick.be/posts/rolling-back-safely/</link><pubDate>Tue, 06 Oct 2026 17:30:00 +0000</pubDate><guid>https://blog.uptick.be/posts/rolling-back-safely/</guid><description>&lt;p&gt;Sooner or later a change goes live that should not have. What matters then is how fast you can undo it, and whether undoing it is safe.&lt;/p&gt;</description></item></channel></rss>