The Road to Easier Shiny App Deployments
summary
Lists concrete checks and fixes for failed Shiny deployments: examine deployment logs (Posit Connect logs tab or server /var/log), remove hardcoded secrets and use environment variables (Connect or .Renviron), ensure DB credentials, firewall and user permissions are correct, include R package and system dependencies (curl, git, TeX) for building, watch platform limits like Max app image size, and use rsconnect, containerization and CI/CD to pin environments and reproduce failures.
AI-written summary · about
chapters (11)
- 0:00Easier Shiny app deployments
- 2:15Two personas in deployment
- 4:46Troubleshooting deployment logs
- 6:10Avoid hardcoded secrets
- 7:55Environment variables for config
- 9:20External resources and dependencies
- 11:06Dependency issues in deployments
- 12:28Resource limits and tuning
- 13:58Proactive deployment strategies
- 15:43Key takeaways and tips
- 16:45Q&A on deployments
related talks
15mA Robust Framework for Automated Shiny App Testing
14mR Shiny - From Conception to the Cloud- 14mR Shiny - From Conception to the Cloud
- 15mA Robust Framework for Automated Shiny App Testing
20mWhat I learned from running Shiny in production
01h 32mCreating Production-Ready Shiny Apps
15mR Markdown + RStudio Connect + R Shiny
32mOperating Rails: what about after you deploy?