Basic problem I want to solve: I want the
mdbook serve experience, but I want to serve multiple books at the same time, and it's too cumbersome to start one mdbook process for each book. (Also, I'm running mdbook through a wrapper because I want to generate some extra metadata).
I'm working on several mdbooks in a project, and I'm linking the books to each other. I have a server which serves all the books at once, and I also have a tool which regenerates whatever book has been modified, much like
mdbook serve does.
This works well, and I'm happy with it, but it could be even better -- if the web client could automatically reload the page once it has been regenerated, just like
mdbook serve does. Anyone have the inside scoop on how the mechanics of automatically reloading the generated HTML in the web browser is implemented? Is it something that one could easily hook into with a different hosting solution? (Specifically Rocket instead of warp).