ShinyProxy 1.1.0 released!

[This article was first published on Open Analytics, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

ShinyProxy is a novel, open source platform to deploy Shiny apps for the enterprise or larger organizations.


In our previous release (see this blog post) we announced our focus on scalability with support for Docker Swarm back-ends. With version 1.1.0 we moved to hyperscaling Shiny apps in the datacenter by adding support for Kubernetes. We have used it for customers that roll out internet-facing Shiny apps with high numbers of concurrent users and needs for automated deployment.

Kubernetes diagram

A Kubernetes back-end can simply be configured using

    container-backend: kubernetes 

and kubernetes specific properties allow to set all typical configurations such as the apiserver URL, certificates for accessing the cluster over https, namespaces for pod creation, definition of the pull policy etc.

ShinyProxy in a container

In a similar vein, we also worked on running ShinyProxy itself in a container on the different backends (Docker, Docker Swarm and Kubernetes). Containerizing ShinyProxy per se is not a difficult exercise (it is nothing more than a single jar file to launch), but one can distinguish two ‘run modes’:

  • ShinyProxy runs inside a container, in the same container manager where it spawns shiny apps, or
  • ShinyProxy does not run inside a container, or as a container in a different container manager.

To operate in this first mode, we introduced a new setting internal-networking which (for the Docker backend) can be set as follows:

      internal-networking: true

If the ShinyProxy container was started in a dedicated network e.g. shinynet, one can indicate that the apps should have interfaces in the same network using the docker-network property:

  - name: beautiful-app
    docker-network: shinynet

If you want to try this out, you can docker pull openanalytics/shinyproxy from Dockerhub.

Python apps ?!

Another new feature in this release is the support of Dash apps. Dash is the equivalent of Shiny in the Python world and built on top of Plotly.js, React, and Flask.

Dash apps will by default run on port 8050, so we added a new port property that can be defined at the level of individual apps:

  - name: dash-demo
    display-name: Dash Demo Application
    port: 8050
    docker-cmd: ["python", ""]
    docker-image: openanalytics/shinyproxy-dash-demo

ShinyProxy Dash Demo

An example Docker image has been published on Docker Hub and, as always, the sources are on our Github page.

With ShinyProxy you can now use one single framework to roll out both R/Shiny apps and Python/Dash apps!

Miscellaneous improvements

Besides the Kubernetes back-end, containerization and the support for Dash apps, we also made a number of small improvements. It is e.g. possible now to have multiple sessions per user/app combination. In other words a user can have multiple browser tabs with the same app in one single or in multiple browsers. Also the LDAP configuration has been extended and documented more elaborately. Finally, on community demand we added the possibility to pass a privileged flag when running a Docker container.

For all these new features, documentation has been updated on and as always community support on this new release is available at

Don’t hesitate to send in questions or suggestions and have fun with ShinyProxy!

To leave a comment for the author, please follow the link and comment on their blog: Open Analytics. offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Never miss an update!
Subscribe to R-bloggers to receive
e-mails with the latest R posts.
(You will not see this message again.)

Click here to close (This popup will not appear again)