Define a configuration for whatever tool to spin up an instance of ./jbitor-web-whatever running in the cloud. Maybe Vagrant would be best, as it would also allow SSH access, and it might be possible to configure it to use either a local Vagrant VM or a cloud server, and could be used in conjunction with some other deployment tools I'm unfamiliar with.
For now this would only be meant for running instances for development or testing, but later it could be used to provision a real server.
The current web interface is being designed from the perspective of being used locally by a single user, not remotely or publicly. For now, the server should probably only serve on 127.0.0.1, requiring you to use something like an SSH tunnel SOCKS5 proxy to access the instance securely. We could consider working towards having something (maybe distinct from the local interface?) which is safe to actually put on the web.
Define a configuration for whatever tool to spin up an instance of ./jbitor-web-whatever running in the cloud. Maybe Vagrant would be best, as it would also allow SSH access, and it might be possible to configure it to use either a local Vagrant VM or a cloud server, and could be used in conjunction with some other deployment tools I'm unfamiliar with.
For now this would only be meant for running instances for development or testing, but later it could be used to provision a real server.
The current web interface is being designed from the perspective of being used locally by a single user, not remotely or publicly. For now, the server should probably only serve on 127.0.0.1, requiring you to use something like an SSH tunnel SOCKS5 proxy to access the instance securely. We could consider working towards having something (maybe distinct from the local interface?) which is safe to actually put on the web.