<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Golang on nemunaire&#39;s blog</title>
    <link>https://www.nemunai.re/tags/golang/</link>
    <description>Recent content in Golang on nemunaire&#39;s blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>blog@nemunai.re (nemunaire)</managingEditor>
    <webMaster>blog@nemunai.re (nemunaire)</webMaster>
    <lastBuildDate>Thu, 23 Apr 2026 08:44:00 +0000</lastBuildDate>
    <atom:link href="https://www.nemunai.re/tags/golang/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Serving custom Go import paths for many modules with nginx</title>
      <link>https://www.nemunai.re/post/vanity-url-go-import-nginx/</link>
      <pubDate>Thu, 23 Apr 2026 08:44:00 +0000</pubDate><author>blog@nemunai.re (nemunaire)</author>
      <guid>https://www.nemunai.re/post/vanity-url-go-import-nginx/</guid>
      <description>&lt;p&gt;When publishing Go code, the usual practice is to distribute the sources directly from the forge that hosts them: &lt;code&gt;github.com/org/project&lt;/code&gt;, &lt;code&gt;framagit.org/org/project&lt;/code&gt;, and so on.&#xA;It is convenient, but it durably ties the import path to the chosen provider.&#xA;The day you migrate from one forge to another, all your users have to update their imports, and every historical fork keeps pointing at the old address.&lt;/p&gt;&#xA;&lt;p&gt;Fortunately, the &lt;a href=&#34;https://go.dev/ref/mod#vcs-find&#34;&gt;&lt;code&gt;go-import&lt;/code&gt;&lt;/a&gt; mechanism lets you decouple the import path from the actual hosting location of the code.&#xA;All it takes is exposing, on a domain of your choosing, an HTML page containing a &lt;code&gt;&amp;lt;meta name=&amp;quot;go-import&amp;quot;&amp;gt;&lt;/code&gt; tag that describes where the sources live.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
