<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cdn on Lankan Lion | Tech Blog</title><link>https://blog.lankanlion.com/tags/cdn/</link><description>Recent content in cdn on Lankan Lion | Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 24 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.lankanlion.com/tags/cdn/index.xml" rel="self" type="application/rss+xml"/><item><title>From /app to app.: A Safe, Phased Migration to a Dedicated Subdomain</title><link>https://blog.lankanlion.com/post/path-to-subdomain-migration/</link><pubDate>Sat, 24 Jan 2026 00:00:00 +0000</pubDate><guid>https://blog.lankanlion.com/post/path-to-subdomain-migration/</guid><description>&lt;p>Migrating a web app from a path-based URL (&lt;code>example.com/app&lt;/code>) to a dedicated subdomain (&lt;code>app.example.com&lt;/code>) sounds simple—until you touch authentication, routing, and API boundaries. The good news: with a deliberate plan and a phased rollout, it can be low-risk—even boring.&lt;/p>
&lt;p>This post outlines a practical approach that worked for us, distilled into phases, traps to avoid, and a reusable checklist.&lt;/p>
&lt;p>This approach is especially useful for &lt;strong>SaaS products, dashboards, and SPAs&lt;/strong> that rely on hosted authentication providers and API-driven backends.&lt;/p></description></item></channel></rss>