No Clocks

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

Display HTML Elements on Full Screen in 'Shiny' Apps Using 'Screenfull.js' - etiennebacher/shinyfullscreen

React.js is a thriving JavaScript library that eases encapsulating and sharing sophisticated component libraries. The React.js ecosystem is filled with components for doing everything from...

Aaaand... because I couldn't help myself. A simple little example using shinyjs that seems to work for my not-very-thorough testing 😄 The two important bits: In the UI: shinyjs::useShinyjs(), In the Server (10 seconds for testing): shinyjs::runjs( "function reload_page() { window.location.reload(); setTimeout(reload_page, 10000); } setTimeout(reload_page, 10000); ") You definitely don't need the shinyjs package to make this work, but it does make things a little easier :s...

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

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

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

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

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

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

devindocker

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 template for deploying R Shiny apps with ShinyProxy in Docker Swarm mode - presstofan/shinyproxy-docker-swarm-demo

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

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

Environment Management with Docker

Contribute to trvinh/PhyloProfileDocker development by creating an account on GitHub.

This post provides a guide to secure ShinyProxy with Nginx, Certbot and AWS Cognito, and monitor usage statistics with InfluxDB, Telegraf and Grafana.

A docker tutorial for reproducible research. Contribute to ropenscilabs/r-docker-tutorial development by creating an account on GitHub.

You can put Shiny Server Pro in a Docker container, but licensing must be handled explicitly. For this configuration, we recommend using a floating license server on hardware or a static VM, on the...

A step-by-step tutorial on creating a web application with Streamlit, building a Docker image with GitHub Actions, and hosting on Heroku.