It also allows us to embed the statistical power of R directly into those web applications. It allows R users to develop powerful web applications entirely in R without having to understand HTML, CSS and JavaScript. Hopefully if you’re reading this you already know, but Shiny is a web application framework for R. Over time though I came to understand the power and flexibility that this model provides and, to a large extent, that’s what this post is about. When he told me this, I was heavily embedded in the publication side and I didn’t immediately understand the implications. Joe told me some time ago, that all you really need in an app.R file is a function that returns a Shiny application object. I’ve figured out some of this for myself, but the most pivotal piece of information came from Shiny creator, Joe Cheng. In this post I’d like to fill in some of the technical background and provide some information about Shiny app publishing and packaging that is hopefully useful to a wider audience. Last year, during some of my conference talks, I told the story of Mango’s early adoption of Shiny and how it wasn’t always an easy path to production for us. The information contained herein has been built up over years of deploying and hosting Shiny apps, particularly in production environments, and mainly where those Shiny apps are very large and contain a lot of code. This article originally appeared on the Mango Solutions blog. (Or, how to write a Shiny app.R file that only contains a single line of code)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |