“ sudo stop shiny-server” followed by “ sudo start shiny-server” is the best way to restart the server- “sudo restart shiny-server” is not a sure bet on any other process.

“ nano /var/log/shiny-server.log” is the location of current shiny logs. The default root folder from which shiny apps are hosted and run is “ /srv/shiny-server” (or just “ /srv” to be safe). This is handy if your server disconnecting when the app tries to run something- it is a simple fix to a problem not always evident in the logs. “ sudo chmod -R 777” is how you change your directory permissions for read, write, and execute (all of those enabled). Don’t bother with instructions that include “apt-get install”, as they are for a different Linux OS! “ sudo yum install” and “ wget” are for fetching and installing things like shiny. For reference, here is some extremely important Red Hat CLI language worth being familiar with and debugging: I am using the AWS “Linux 2” AMI, which is based on the Red Hat OS. All of this info is accessed via SSH, to the server running Shiny and RStudio. It turns out hosting a Shiny Web app provides a large number of opportunities for things to go wrong…. I plan to do a more thorough demo on this- particularly the use of the $ symbol, as in “input$output”- later. Learning the syntax to convert R code into a Shiny app is rather subtle, and can be hard.

A common way to do this is the R-specific tool Shiny, which is built in to RStudio.

Info on deploying a Shiny web app in R using AWS (EC2 Redhat)Īs a follow-up to my post on how to create an AWS RStudio server, the next logical step is to host some useful apps you created in R for people to use.

Aws shiny server