ShinyProxy is a novel, open source platform to deploy Shiny apps for the enterprise or larger organizations. Full Kubernetes Support One of the main advantages of ShinyProxy is the use of plugable container back-ends which allows people to use ShinyProxy on a plain Docker host, on a Docker Swarm cluster or on internet-scale Kubernetes cluster in the cloud. The way organizations have been deploying ShinyProxy on Kubernetes clusters has grown exponentially and providing a means to configure ShinyProxy tailored to the specific Kubernetes setup became more important.
ShinyProxy is a novel, open source platform to deploy Shiny apps for the enterprise or larger organizations. Secured Embedding of Shiny Apps Since version 2.0.1 ShinyProxy provides a REST API to manage (launch, shut down) Shiny apps and consume the content programmatically inside broader web applications or portals. This allows to cleanly separate the responsiblity for the Shiny apps (data science teams) and those broader applications (IT teams) while still achieving seamless integration between the two from the user’s perspective.
ShinyProxy is a novel, open source platform to deploy Shiny apps for the enterprise or larger organizations. Since our previous blog post five releases took place, so it is time to provide the ‘state of affairs’ before venturing into the New Year. Kerberos and Co To some Kerberos is a multi-headed dog that guards the gates of the Underworld. To others it is enterprise technology that protects corporate networks and offers single sign-on for network services.
ShinyProxy is a novel, open source platform to deploy Shiny apps for the enterprise or larger organizations. Embedding Shiny Apps Although Shiny apps are very popular for interactive data analysis purposes, many organizations communicated a need to more closely integrate these apps within larger applications and portals. In previous releases we broke down the walls to make this happen: hiding the navbar, single-sign on, theming the landing page and advanced networking support were only a few steps in that direction.
ShinyProxy is a novel, open source platform to deploy Shiny apps for the enterprise or larger organizations. Theming ShinyProxy 1.1.1 is in essence a maintenance release, but there is one new feature that has been on the wish list of our users for a long time: the possibility of theming the landing page of ShinyProxy which displays the overview of the Shiny apps. The standard display when using the ShinyProxy demo image from the Getting Started guide is a plain listing:
ShinyProxy is a novel, open source platform to deploy Shiny apps for the enterprise or larger organizations. Scalability 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.
ShinyProxy is a novel, open source platform to deploy Shiny apps for the enterprise or larger organizations. Since our last blog post ten new releases of ShinyProxy have seen the light, but with the 1.0.2 release it is time to provide an overview of the lines of development and advances made. Scalability ShinyProxy now allows to run 1000s of Shiny apps concurrently on a Docker Swarm cluster. Moreover, ShinyProxy will automatically detect whether the Docker API URL is a Docker Engine API or a Swarm cluster API.
In our last blog post we mentioned the need people felt to integrate Shiny apps in content management systems like Drupal. Release 0.7.8 added one extra feature in this respect so people could also include ShinyProxy hosted Shiny apps in external iframes. It also kicked-off our effort to support service scalability and ever more complex apps. In the scalability area, we introduced facilities to manage and set memory limits on individual Shiny applications.
Since the last release (see this blog post), we received two interesting use cases for which we did not imagine ShinyProxy would be used. First of all, we received a request to support other authentication methods than LDAP authentication. Whereas ShinyProxy is currently used primarily by larger organizations and companies that typically work with LDAP-based authentication systems, it seems people appreciate the elegance of the framework also for more small-scale use.
Our previous post on the how and why of ShinyProxy triggered a lot of encouraging reactions. Here’s our favorite: Indeed choosing for Docker opens a world of possibilities for ShinyProxy and making you no longer dependent on a particular version of R or shiny is only one of the advantages. We also received a number of useful suggestions and decided to quickly release the new features and fixes as version 0.