Jake Howard

The file serving component of `traefik-pages` was always the one I was least happy with, mostly because there's so much scope for customization. Handing that off to some other process...

I agree lunr probably isn't ideal, as the index will be huge. [I've written client-side search with Hugo](https://theorangeone.net/posts/hugo-website-search/), and it's very simple, but the index may be large given the...

It's not just heavy in terms of resource. It also makes local development much more of a pain, not to mention is more complex to setup and work with anyway....

Much of the code from this was based on https://github.com/selfhostedshow/show-notes, which is under GPL 3. With the code being in the state its in now, you'll likely need unanimous agreement...

It definitely works with `whitenoise` - I've had it running on my site for a while. Do make sure you're on the latest version though. I'm not seeing anything obvious....

Closing due to lack of information.

> In areas that expect to deal with `.path` in any manner `urlparse` should continue to be used Makes sense to me! I'll get this updated shortly. > not to...

Most use cases of `urlparse` didn't touch the path, so they can be converted to `urlsplit` just fine. Most of those which do use `.path` simply parse the URL, mutate...

I'm not really a Go person, hence it's a bit thrown together. Although IMO #3 is more complex and harder to read.

Merged in https://github.com/wagtail/wagtail/commit/95eac5ab7801a624451ce53fe0eb94763d07bb9e - thanks!