Tobia De Koninck

Hi, as you noticed ShinyProxy works fine with rootless docker, although it's important that ShinyProxy is using the same user, such that it's able to access the docker socket (the...

@dylancis this has changed in ShinyProxy in 3.0.0, because it's needed for various features of ShinyProxy (multiple app instances, app pre-initialization, crash detection, shinyproxy operator etc). For what reason do...

@dylancis in that case it's best to generate an url to `https://your-instance.com/app//..`. When users click on this URL they benefit from all client-side features. If you want to dynamically generate...

Hi I believe this issue has been solved or has become outdated, therefore I'm going to close it. If you still experience this problem, feel free to re-open the issue....

Hi It should be possible to add TLS to ShinyProxy using the Spring Boot configuration, see e.g. https://spring.io/blog/2023/06/07/securing-spring-boot-applications-with-ssl and https://docs.spring.io/spring-boot/how-to/webserver.html#howto.webserver.configure-ssl . However, I did not try this yet. An alternative...

Hi I believe this issue has been solved or has become outdated, therefore I'm going to close it. If you still experience this problem, feel free to re-open the issue....

Hi The reason that we don't add the owner reference is that ShinyProxy needs full control over the pods. When using the Kubernetes operator (https://github.com/openanalytics/shinyproxy-operator), new ShinyProxy serves are started...

Your proposal would work when the applications hosted by ShinyProxy are stateless. However, in our experience, the majority of applications deployed using ShinyProxy are in fact stateful. This is the...

Hi I believe this issue has been solved or has become outdated, therefore I'm going to close it. If you still experience this problem, feel free to re-open the issue....

Hi, thanks for opening this issue. It seems all RPM based distro use `java-17-headless` as the common name for the java package, therefore I now changed our package to us...