I use it all the time.
I am not sure how significant (if any) changes were made since then.
I've just checked and the version of leo-ver-serv on my computer is the same as on the github.
So, I suggest that you install rust if you don't already have it. The best way is to install rustup first (
https://rustup.rs/)
Then using rustup install the latest tool-chain for rust:
rustup toolchain install nightly
Then you can just run the following command:
cargo install leo-ver-serv
If you find that this doesn't work for you, or after starting leo-ver-serv you get some errors in the console, please file the issue on the github, or ask here for further help.
For the plugin to work correctly, leo-ver-serv should be running and full path to the outline should be in the list of known files that was given to leo-ver-serv on the start. This means if you create a new outline, or if you open some outline that is not listed in your recent Leo files, you'll probably have to restart leo-ver-serv.
This limitation can be lifted, however, leo-ver-serv has to create and open a sqlite3 database for any filename it receives request for. So, theoretically speaking, if an attacker can manage to send the requests to your leo-ver-serv, it would be possible to cause creation of too many files just by sending requests for nonexistent filenames. To prevent this kind of attack, leo-ver-serv will bind only on localhost and will refuse to handle requests for filenames that are not among known files.
While I am writing this, I have just realized that perhaps it would be enough just to check if the filename exists and is Leo file. In that case leo-ver-serv won't need list of known files at all.
I think I should put some more work on the web view displaying versions of Leo. The outline view lacks scrolling, so it is sometimes hard or impossible to see nodes close to the bottom of the outline.
Vitalije