rust-websocket currently has no option to disable ssl support. We can either try to change that upstream (didn't look at it yet) or switch to another websocket library (e.g. ws-rs).

Woah this is awesome!

It will take me some time to review this because I am not very familiar with the dependencies and it's a pretty substantial contribution ;)

rust-websocket currently has no option to disable ssl support. We can either try to change that upstream (didn't look at it yet) or switch to another websocket library (e.g. ws-rs).

That is the cause of the failed tests, right?
Maybe this is something we could ask on users.rust-lang.org to get feedback of people who have already tried some of them.

Ok, ws-rs has ssl support as an optional feature and provides a broadcaster function which allows the whole livereload stuff to be reduced to 20 LOC...

I just tested this locally and it seems to work very well. It is amazingly useful and will surely be a huge time saver for a lot of people! 👍

There is just one small thing, when you stop serving, the code for the web-socket is still present in the rendered files. It's really no biggie and it can be resolved by just doing a mdbook build, but improving this could be an idea for a future improvement 😉

Anyway, very good job with this

@azerupi Can you push an update to crates.io? :)

Yes I'll do that right now :)