running qvis locally

[marten-seemann]

It's quite hard to run qvis locally, since there's a number of bash scripts that are run (some using sudo, which is a permission level I don't want to grant to docker), and because it assumes that it's running on a public server, and requires a TLS certificate.

Things could be simplified by using docker-compose. This could be used to specify the dependency between the two Docker containers, and starting them could be as simple as running docker-compose up.

It would also be nice not to conflate running the local server (which should be running on HTTP), and the server frontend in front of it. I've made good experience with just running a Caddy server in a separate Docker container, as Caddy deals with the TLS config automagically - no need to obtain and renew TLS certificates any more. Caddy would run in reverse proxy mode and just proxy HTTPS requests from the public internet to the qvis-server Docker container.

[marten-seemann]

Just figured out that the easier way to run qvis locally is by running the npm commands in https://github.com/quiclog/qvis/tree/master/visualizations.

Feel free to close this issue.