[Jedd]

Sounds like an easy way to solve both problems. Does it cache the fandom site, pull it all down, or it's just a redirector / re-theming front-end and makes calls out to fandom for each page load?

I skimmed the docs looking for an architecture overview, but couldn't see an answer to this. The low resource requirements cited for the docker container install suggest it's just doing page-loads and re-rendering them.

EDIT: So I've now set this up as via docker on my nomad cluster, and it's just proxying the pages and searches to and fro. It's a bit heavy - sitting at about 410MB while idle, but doesn't feel like there's any performance impact compared to hitting upstream directly.