1 hour ago · Tech · 0 comments

I've been building hobby projects for years. Normally I'll give the better ones a write-up here and a link to GitHub Pages, but the project itself lives at khawkins98.github.io/project-name/. I wanted to bring them on-domain without the obvious headaches: dozens of subdomains is more infrastructure than any of these deserve, subdomains still confuse people, and copying build output into the main repo defeats the point of keeping them separate. Could I just have my site do what GitHub Pages already does: proxy /repo-name/ to whatever GitHub is already serving? Before: khawkins98.github.io/PDF-A-go-go After: AllAboutKen.com/PDF-A-go-go Same project, same deploy pipeline, better home. See the garage Keep reading if you want to see exactly how I wired it up. tl;dr# Vercel rewrites proxy /project-name/:path* to the GitHub Pages origin — no deploy changes required A naive rewrite 404s on the project root; two redirects entries (bare path and trailing slash → /project-name/index.html) fix it…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.