Migrating from plain docker to shinyproxy operator with docker

I currently have 2 shinyproxy servers (1 public, 1 with auth) running on a single machine. I use Nginx to route traffic to the ports each shinyproxy docker container is running on via domain paths like https://mydomain.com/public and https://mydomain.com/secure (I add the appropriate context-path to each shinyproxy config). I also have some other services running on other ports that Nginx directs requests to. I have SSL setup using certbot.

Having seen the news that the shinyproxy operator is now available with docker and can be used to host multiple shinyproxy server instances like my use case above, I’d like to try this out and benefit from all the addition features it offers. But I’m currently confused as to how to migrate my current setup to an operator setup…

Can I still use my Nginx reverse proxy to direct traffic to the shinyproxy operator? What port does it run on? Can I use my current SSL certs or does the operator create its own? If I launch 2 separate shinyproxy servers on the operator, how do you access each and what would the domain path look like?

Thanks!

Hi

Thanks for explaining your use-case. The operator uses caddy as a reverse proxy, even when using multiple ShinyProxy servers with different hostname or sub-paths. SSL/TLS is not required and is disabled by default. In principle you can put a different reverse proxy in front of caddy, but currently we hard-coded caddy to use port 80 (and 443), see Configuring ShinyProxy Operator 2.2.0 to Use a Custom Port (e.g., 8080) with IP Address Access · Issue #65 · openanalytics/shinyproxy-operator · GitHub .

We are planning to add a configuration option to use a different option, and then you are able to put nginx in front of it.

It’s quite a small change to have the port configurable (see shinyproxy-operator/src/main/kotlin/eu/openanalytics/shinyproxyoperator/impl/docker/CaddyConfig.kt at master · openanalytics/shinyproxy-operator · GitHub) , so if you are able, feel free to open a PR.