<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tutorial on vanityURLs</title><link>https://www.vanityurls.link/en/tags/tutorial/</link><description>Recent content in Tutorial on vanityURLs</description><generator>Hugo</generator><language>en-CA</language><lastBuildDate>Thu, 14 May 2026 23:58:58 -0400</lastBuildDate><atom:link href="https://www.vanityurls.link/en/tags/tutorial/index.xml" rel="self" type="application/rss+xml"/><item><title>Redirects as Code: Managing Short Links the GitOps Way</title><link>https://www.vanityurls.link/en/blog/redirects-as-code/</link><pubDate>Mon, 10 Mar 2025 00:00:00 +0000</pubDate><guid>https://www.vanityurls.link/en/blog/redirects-as-code/</guid><description>&lt;p&gt;Most URL shorteners are black boxes. You log in through a web UI, create a link, and hope the service stays running. When something breaks — a link stops working, a campaign URL points to the wrong page, someone accidentally deleted a redirect — there&amp;rsquo;s no audit trail, no rollback, no way to know who changed what and when.&lt;/p&gt;
&lt;p&gt;vanityURLs takes a different approach: your redirects live in a plain text file, in a Git repository, deployed via Cloudflare Pages. This is GitOps applied to URL management.&lt;/p&gt;</description></item></channel></rss>