Here in Belgium, World Cup fever is at fever pitch, but with matches starting during work hours, how is a desk worker supposed to follow along? By leaving the R environment? Blasphemy. Today we show how to use R to generate live desktop notifications for The Beautiful Game. A notification system preview, free of local bias. Overview We break the process of producing a live score notification into the following steps:
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.
Phaedra is an open source platform for data capture and analysis of high-content screening data. With the release of Phaedra 1.0.2, we are taking another step towards our goal of unprecedented flexibility in supported setups, ranging from a single small Mac desktop to a cloud-based infrastructure with multiple servers and an array of mixed Windows/Mac/Linux clients. The initial release of Phaedra supported only the Windows platform. Update 1.0.1 introduced Phaedra on the Mac and Linux desktops, and allowed you to deploy a DataCapture server on Linux servers as well.
Motivation Have you ever had the feeling that the creation of your data analysis report(s) resulted in looking up, copy-pasting and reuse of code from previous analyses? This approach is time consuming and prone to errors. If you frequently analyze similar data(-types), e.g. from a standardized analysis workflow or different experiments on the same platform, the automation of your report creation via an R ‘template’ package might be a very useful and time-saving step.
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.
Organising useR!2017 was a challenge but a very rewarding experience. With about 1200 attendees of over 55 nationalities exploring an interesting program, we believe it is appropriate to call it a success - something the aftermovie only seems to confirm. Behind the Scenes To give you a glimpse behind the scenes of the conference organization, Maxim Nazarov held a lightning talk on ‘redmineR and the story of automating useR!
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.