Replies: 2 comments 6 replies
|
Hi, A workaround for shiny would be to deploy a reverse proxy in addition (e.g. like in the small Flask app below), that is able to route incoming requests to The following example (set up in a docker container with shiny and a minimal leafmap example shiny-app) does work. However, I have not tested it with several layers / or maps and I have not investigated security issues yet (so I would not try this on a web-facing server)... P.S.: by setting debug=True one can track the network traffic / requests... In the shiny-app the tile client is then set up like this (assuming that the flask-proxy is running on host "my-flask-proxy.com" and port 8888): |


See #677