After some fiddling around with PaaS services I reinstated the original site search, which, being based on
SQLite‘s FTS engine, still manages to be better than DuckDuckGo’s or Google’s.
It is now the only non-static URL on the site, and hosted on a separate compute resource. As it turns out, using Azure Cognitive Search and Azure Functions would have worked just as well, but taken too much time to hack into the static site generator–which was still using
SQLite anyway for backlinks, so why waste a perfectly good index?
I’m honestly amazed at the mileage I’m getting from that code…