Support

RStudio professional product requirements

Follow

Summary

RStudio professional server products are powerful tools for doing data science. As such, they require modern operating systems and browsers as described in our Platform Support. RStudio professional server products also require the following:

  1. Root privileges for installing and running
  2. Configuration to a user authentication scheme
  3. Access to the R programming language and an R repository

We encourage you to make R an analytic standard in your organization. If you need help sizing your server, please see our Configuration and Sizing Recommendations. If you need help installing R on your server, please see our guide to installing Multiple Versions of R. Finally, if you are interested in discussing how to best use R with your specific environment, please contact our expert sales team.

Detail

1. Root privileges for installing and running

All RStudio professional server products require root privileges for installing. Note that system-wide installation of R on Linux typically requires root also. Additionally, some RStudio products require root while running: RStudio Server Pro runs as the root user in order to create new R sessions on behalf of users; RStudio Connect runs as the root user in order to isolate applications and processes; and Shiny Server Pro requires root for many of its most useful features. RStudio Package Manager typically installs as root, but does not require root for installing or running.

2. Configuration to a user authentication scheme

RStudio professional server products are configurable with LDAP, Active Directory, and PAM. If needed, single-sign-on authentication can be configured using proxied authentication. In this configuration all traffic to the application server is handled by a proxy server which also handles user authentication.

Only RStudio Server Pro requires local accounts regardless of what RStudio authentication method you use. You should set up local accounts manually and then map authenticating users to these accounts. You can also use PAM Sessions to mount your user home directory to the server. Note: Shiny Server and RStudio Connect serve end users, not R developers, so these products can be configured without local accounts.

3. Access to the R programming language and an R repository

New packages produced by the R community often require a version of R produced within the past few years, so R users will typically need a modern version of R and a C++11 compiler in order to benefit from the ecosystem of packages available. RStudio’s products typically target compatibility with R version 3.1.0 and greater. We recommend upgrading R yearly. Versions of R can be obtained by various means, the most common of which is installing a binary version from a standard repository. To install additional versions of open-source R side-by-side you will need to build R from source. We recommend building R from source rather than using your system’s package manager in order to ensure that the version of R installed on your server won’t unexpectedly change.

Users and administrators will need to frequently update new versions of R packages. The most common way to install R packages today is to download them from the CRAN repository via the Internet. If your system is not connected to the Internet for security purposes, you should either set up a you own repository or use RStudio Package Manager

References

Comments