Replacing a Public Linkding Instance with a Static Site

TL;DR: I stopped exposing my homelab's dynamic Linkding instance to the public internet via Tailscale. Instead, I built linkding-ssg, a self-contained Go CLI that snapshots my 35,000 bookmarks into a fast static site with client-side Pagefind search—embedded binaries, Ivy Bridge quirks, and all. Photo by Jan Antonin Kolar on Unsplash Hosting overkill I’ve been running Linkding in my homelab for a while now to collect bookmarks. It’s a great app—clean UI, snappy, and it plays nicely with the rest of my feed reading Rube Goldberg machine. And, until tonight, I had my cloud VPS reverse-proxying links.lmorchard.com directly back into my home network over Tailscale so anyone on the web could browse my links. It was neat & clever to set up, but I realized how silly it was. I’m the only person who adds, tags, or edits bookmarks in this collection. Why was I exposing a dynamic Django application to the public internet, tunneling inbound web traffic straight into my home server, and fretting…