<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>migrations on krtffl.dev</title>
    <link>https://krtffl.dev/tags/migrations/</link>
    <description>Recent content in migrations on krtffl.dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© [krtffl](https://krtffl.dev)</copyright>
    <lastBuildDate>Mon, 18 Nov 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://krtffl.dev/tags/migrations/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>shipping a single self-contained go binary</title>
      <link>https://krtffl.dev/posts/self-contained-go-binary/</link>
      <pubDate>Mon, 18 Nov 2024 00:00:00 +0000</pubDate>
      
      <guid>https://krtffl.dev/posts/self-contained-go-binary/</guid>
      <description>&lt;p&gt;picture it: a fresh vps, your ssh key just accepted, a blank box that has never heard of your app. you &lt;code&gt;scp&lt;/code&gt; up a binary. then you &lt;code&gt;scp&lt;/code&gt; up a &lt;code&gt;config.yaml&lt;/code&gt;. then you remember the database is empty, so you &lt;code&gt;apt install&lt;/code&gt; the migrate cli, &lt;code&gt;scp&lt;/code&gt; up the &lt;code&gt;migrations/&lt;/code&gt; folder too, point one at the other, and pray the versions line up. four artifacts and a small ceremony, just to watch the thing print a banner and die because the config key got renamed two commits ago.&lt;/p&gt;
&lt;p&gt;i did that dance one too many times on a little learning project and thought: why does a single go binary need a goddamn support convoy to boot?&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
