I wanted to know what others think is the best approach when making a shiny module that uses some functions/variables that in a non-module app would belong in global.R Do you still keep them in global.R? To me that seems to break the isolation and independence of modules, since a module should be explicit about all its inputs and outputs. As a concrete example: in the following app, the module UI and module server use a variable defined outside of it. Here's one way to write it: foodata

Docker images for R. Contribute to rstudio/r-docker development by creating an account on GitHub.

an opinionated environment for compiling R. Contribute to rstudio/r-builds development by creating an account on GitHub.

I need to set the column width of a DataTabe in an R Shiny app. I went through the Data Table Options in the documentation. Also, I reviewed this and this questions in Stackoverflow. Setting width

A template for deploying R Shiny apps with ShinyProxy in Docker Swarm mode - presstofan/shinyproxy-docker-swarm-demo

A package to help deal with devtools::check outputs - ThinkR-open/checkhelper

Repository with DockerFiles for tutorials. Contribute to ThinkR-open/docker4dev development by creating an account on GitHub.

Repository with DockerFiles for tutorials. Contribute to ThinkR-open/docker4dev development by creating an account on GitHub.

A Collaborative list of things to know before submitting to CRAN - ThinkR-open/prepare-for-cran

devindocker

Package your RShiny app into a docker container for local deployment. No rshiny-server or special rshiny.conf configurations necessary!

Authoring Books and Technical Documents with R Markdown - rstudio/bookdown

This document is full of supplemental resources and content from the Shiny in Production Workshop delievered at rstudio::conf 2019.

A Chrome extension for recording browser interaction and generating Puppeteer & Playwright scripts

Making the web more beautiful, fast, and open through great typography

R Shiny app for iAtlas (new, 2020 version). Contribute to CRI-iAtlas/iatlas-app development by creating an account on GitHub.

Data Scientist. Shiny Developer. Tidyverse Denizen. Scheme Enthusiast.

Docking or containerization is a new method of distribute a software/tool. Beside providing only the source code for installing, we give the users the so-called container, which contains the whole environment to run the program, including the tool and its dependencies with the exact version and all the needed configurations. By delivering such a “container”, users are always able to “reuse” the tool and reproduce the results as we did.

Write an awesome description for your new site here. You can edit this line in _config.yml. It will appear in your document head meta (for Google search results) and in your feed.xml site description.

Easily Extracting Information About Your Data. Contribute to cosimameyer/overviewR development by creating an account on GitHub.

Shiny App for Load Balancing. Contribute to sjewo/shiny-loadbalancer development by creating an account on GitHub.

This post provides a guide to effectively and securely scale your ShinyProxy deployment of shiny apps in production with Docker Swarm and Traefik

Don't believe the documentation! Shiny modules aren't just for advanced users; they might just be a great entry point for development

rocker/rbase docker image with a selection of packages preinstalled geared to support R-Shiny based webapp. - slink42/rbase_shiny