shinyproxy 2.4.0 loses reactivity when containerized
See original GitHub issueShinyproxy 2.4.0. running in docker containers cause shiny apps to lose reactivity - only with shinyproxy 2.4.0, not with previous versions.
The issue can be experienced by applying the following example:
Replacing 2.4.0
in the Dockerfile
with 2.3.1
does not experience the same issue - everything works as expected with 2.3.1.
Attached are two screen captures demonstrating the issue with v2.3.1 and v.2.4.0, respectively.
Thanks and kind regards sandro
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
FAQ | ShinyProxy
it is very likely that your container was started, but that the Shiny app itself could not be started properly. This almost always...
Read more >ChroMo, an Application for Unsupervised Analysis of ... - MDPI
The web access is behind a Docker containerized Nginx reverse proxy. ... is much lower in the absence of Hrs1, oscillatory movement is...
Read more >Daily R Archives - Netlify
Functional programming explains why containerization is needed for reproducibility; 2022/11/30 Statistical Modeling, Causal Inference, and Social Science
Read more >How to Set Up ShinyProxy to Host Shiny Apps
ShinyProxy is a free and open-source platform to deploy containerized web ... Hello Shiny App description: A simple reactive histogram container-cmd: ["R", ...
Read more >ShinyProxy 2.4.0 - Open Analytics
One of the main advantages of ShinyProxy is the use of plugable container back-ends which allows people to use ShinyProxy on a plain...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the heads up, these were forgotten during the rebuilds… The correct version is now also available at Github releases.
In that case the file in the releases is not the correct one, because it’s shasum differs:
This matches the SHA256 checksum mentioned in the
shinyproxy-2.4.1.jar.sha256
file.