Deploy R and Shiny
summary
Compares deployment options: shiny server open source runs one app per R process, has no built‑in authentication and needs Linux/sysadmin work but is cheap to start; shiny server pro adds configurable auth and better scaling for a cost; shinyproxy builds on Docker for immediate scalability and any auth backend but requires managing images and a single YAML config that controls all apps; RStudio Connect provides web UI for publishing, URLs, scheduling, reports and enterprise auth with paid support, reducing ops effort.
AI-written summary · about
chapters (9)
- 0:00Introduction to Shiny deployment
- 3:17Who needs Shiny deployment
- 7:14Self-hosted vs cloud options
- 7:35Shiny Server open source
- 9:50Shiny Server Pro features
- 10:31Shiny Proxy overview
- 13:22RStudio Connect advantages
- 16:08Choosing the right platform
- 17:15Q&A and support options
related talks
25mReproducibility Around a Web Application
20mWhat I learned from running Shiny in production
19mConfiguration management tools for the R admin
17mBuilding a data science pipeline for the FT with RStudio Connect
58mThe Past and Future of Shiny
22m. Cultivating Your Own R Ecosystem as a Solo Contributor
24mR Consortium initiatives in medicine
54mR Not Only In Production