<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>BitPage</title><link>https://bitpage.me/</link><description>Recent content on BitPage</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 24 Jul 2026 11:35:00 +0000</lastBuildDate><atom:link href="https://bitpage.me/index.xml" rel="self" type="application/rss+xml"/><item><title>About</title><link>https://bitpage.me/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://bitpage.me/about/</guid><description>About BitPage is a pseudonym. This blog runs anonymously — what matters here are the fixes, not the names. Here&amp;rsquo;s who&amp;rsquo;s behind it.
I&amp;rsquo;m the person people call not to &amp;ldquo;build us a website,&amp;rdquo; but when &amp;ldquo;everything&amp;rsquo;s down, figure it out.&amp;rdquo;
I taught myself to code long before my first job in IT. Nobody wanted to hire a self-taught developer without experience, so I got in through QA: two years hunting other people&amp;rsquo;s bugs before I wrote a line of production code myself.</description></item><item><title>How to migrate a stateful Docker app off a server with a dying disk</title><link>https://bitpage.me/infra/migrate-docker-app-dying-disk/</link><pubDate>Fri, 24 Jul 2026 11:35:00 +0000</pubDate><guid>https://bitpage.me/infra/migrate-docker-app-dying-disk/</guid><description>Short answer: When the source server&amp;rsquo;s disk fails on writes but still reads fine, treat it as read-only hardware. Stream pg_dump -Fc over SSH straight to the target machine, pull Docker images from your registry instead of rebuilding end-of-life Dockerfiles, and anchor every rsync exclude with a leading slash. That moved a 14-service app with a 12 GB PostgreSQL database onto a new node without a single write to the failing disk.</description></item></channel></rss>