Just my 2 cents, but assuming the computation needed between incoming data and what has to be displayed is low, I'd go with the 1). -A small webserver on the r

Just my 2 cents, but assuming the computation needed between incoming data and what has to be displayed is low, I'd go with the 1). -A small webserver on the raspbian that takes data feed and updates in realtime through websocket (any lib in go, python, JS, or whatever will do the work, see https://github.com/search?q=websocket&type=repositories https://github.com/search?q=websocket&type=repositories, pick your poison) -An ssh connection to the pi to restart the server or update the code/package -Think of how to deliver the code/package to the pi from the git repo, -One last thing, even it does not seem a critical app supervise the service/get some metrics on the pi if you can And voilà