Package Manager 1.1.0 - No Interruptions | RStudio Blog
No interruptions. That was our team’s goal for RStudio Package Manager 1.1.0 - we set out to make R package installation fast enough that it wouldn’t interrupt your work. More and more data scientists use Linux environments, whether to access extra horsepower during development or to run production code in containers. Unfortunately, the rise in Linux environments has seen a corresponding increase in package installation pain. For Windows and Mac OS, CRAN provides pre-compiled binary packages that install almost instantly, but the same binaries are not available on Linux.
Customizing Package Build Options – RStudio Support
Customizing Package Build Options Overview There are three R package build commands used by the RStudio package development tools: R CMD check R CMD build R CMD INSTALL It's possible to c...
Enabling use of private packages on github.com – RStudio Support
You can now use your proprietary R packages in your shinyapps.io environment. To do so, your package does need to be hosted on in a private github repository (public github repositories have alway...
Upgrading from Open-Source to Pro If you currently have Shiny Server Open-Source installed and want to upgrade to the Pro version, the process is very simple. You can do so with no worries about y...
Common dependencies for Shiny Server – RStudio Support
If you are installing Shiny Server or Shiny Server Pro on an offline server, you may need dependencies installed in order for Shiny Server to install correctly. Below you will find a list of common...
Shiny Server Quick Start: Host a directory of applications – RStudio Support
This article is adapted from the Shiny Server Administrator's Guide for version 1.4.2. This is the default configuration that Shiny Server will use until you provide a custom configuration in...
Shiny Server Quick Start: Let users manage their own applications – RStudio Support
This article is adapted from the Shiny Server Administrator's Guide for version 1.4.2. Some administrators of Shiny Server would prefer to give users -- or some trusted subgroup of users -- t...
Root requirements for Shiny Server – RStudio Support
Shiny Server requires root privileges for installation and certain operations. Note that root privileges are also required for installing R. sudo yum install Rsudo yum install --nogpgcheck
Shiny Server Quick Start: Run Shiny Server on multiple ports – RStudio Support
This article is adapted from the Shiny Server Administrator's Guide for version 1.4.2. This guide will describe how to run Shiny Server on multiple ports simultaneously, and also how to run a...
How to pass authentication credentials to a database using Kerberos – RStudio Support
Overview This article describes how to configure RStudio Server Pro and Shiny Server Pro so that authenticated users can access databases without having to authenticate again. These instructions ar...
Where to store your Shiny application data – RStudio Support
If your Shiny app requires data to run, you can bundle the data with your app or you can reference the data inside your app. Shiny Server does not require a database. Instead it will work with your...
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...
Scaling and Performance - Tuning Applications in Shiny Server Pro – RStudio Support
Shiny Server Pro allows you to scale Shiny applications to support multiple simultaneous users. The scaling is accomplished by setting 3 arguments in the configuration file (/etc/shiny-server/shiny...
Spelling Dictionaries Overview RStudio uses the Hunspell engine for spell-checking on Linux and Windows. Hunspell is also used by a wide-variety of other products including Chrome, Firefox, and L...
Comment Headers in RStudio Sources – RStudio Support
Starting from RStudio 1.2.937, the following file sources support custom commands while sourcing them: R, D3 and SQL file sources. This is accomplished by specifing a !source or !preview comment he...