<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Go Modules on GoMod Vanity URLs</title><link>https://gomodvanityurls.com/tags/go-modules/</link><description>Recent content in Go Modules on GoMod Vanity URLs</description><image><title>GoMod Vanity URLs</title><url>https://gomodvanityurls.com/images/og-default.png</url><link>https://gomodvanityurls.com/images/og-default.png</link></image><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 14 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://gomodvanityurls.com/tags/go-modules/index.xml" rel="self" type="application/rss+xml"/><item><title>Wildcard Routing: One Rule to Manage 50 Go Modules</title><link>https://gomodvanityurls.com/blog/wildcard-routing/</link><pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate><guid>https://gomodvanityurls.com/blog/wildcard-routing/</guid><description>Stop adding vanity URL routes one by one. gvu wildcard routing covers every repo in your GitHub org — or every module in your monorepo — with a single rule.</description></item><item><title>Go Monorepo in Practice: Managing Multiple Modules with Vanity URLs</title><link>https://gomodvanityurls.com/blog/go-monorepo-vanity-url/</link><pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate><guid>https://gomodvanityurls.com/blog/go-monorepo-vanity-url/</guid><description>A hands-on guide to using Go 1.25 subdirectory modules with vanity URLs. One monorepo, multiple importable Go modules, clean branded import paths — powered by gvu --subdir.</description></item><item><title>From IP Addresses to a Branded Domain: One Go Team's Vanity URL Journey</title><link>https://gomodvanityurls.com/blog/from-ip-to-brand-domain/</link><pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate><guid>https://gomodvanityurls.com/blog/from-ip-to-brand-domain/</guid><description>A real Go team story: from the chaos of using IP addresses as import paths to managing 50 internal modules with vanity URLs. New hires understand instantly, server migrations have zero code impact, and branding is unified.</description></item><item><title>Set Up a Custom Import Path for Your Go Module in 30 Seconds</title><link>https://gomodvanityurls.com/blog/30-second-vanity-url-setup/</link><pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate><guid>https://gomodvanityurls.com/blog/30-second-vanity-url-setup/</guid><description>Step-by-step tutorial: create a vanity URL for your Go module in 30 seconds using gvu. Supports custom domains, wildcard routing, and automatic major version handling.</description></item><item><title>Why Your Go Private Modules Shouldn't Use Raw GitHub Paths</title><link>https://gomodvanityurls.com/blog/why-not-github-import-path/</link><pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate><guid>https://gomodvanityurls.com/blog/why-not-github-import-path/</guid><description>From vendor lock-in to IP exposure, using raw GitHub/GitLab paths for Go private module imports has four hidden risks. Vanity URLs are the standard solution recommended by the Go team.</description></item></channel></rss>