Summary of Posit Workbench Installation
1 Installation Planning
Now that you have been through all the steps required to install and configure Posit Workbench, let’s summarize what you have learned and things to consider as you prepare installing it on your own infrastructure. This section reviews things to consider when planning your installation.
1.1 System Requirements
Review the System Requirements section of the Admin Guide to understand the requirements for a Workbench installation.
- Are these requirements acceptable?
- Do you anticipate any challenges in meeting these requirements with your current infrastructure?
- What type of architecture will you be using for your Workbench installation?
1.2 Environment Configuration
- Which version(s) of R do your developers require?
- Do any of the R packages they use require system dependencies you will need to install?
- Which version(s) of Python do your developers require?
- Which version(s) of Quarto do your developers require?
- Which repositories will your developer use for R packages? for Python packages? Are there any concerns with using pre-compiled binaries for the R packages?
1.3 Security, Certificates, and Authentication
- Will you need to get security approvals?
- Do you know where you will get the SSL/TLS certificates you will need?
- Check that the full certificate chain is available in your certificate
- Make sure that the private key for your certificate is not protected with a passphrase
- Do you know where you will be able to get the information you need to integrate your authentication system with Posit Workbench? (e.g., Client URL, ID, and Secret for OIDC)
- How are you going to decide the Workbench roles user will have in your organization?
When planning a Posit Workbench installation, we highly recommend setting up an Architecture Review with a Posit Solutions Engineer. An Architecture Review will ensure you understand the requirements for your target architecture. You will also receive a custom installation guide to help you during the installation process.
This material attempts to stay aligned with information typically covered in an Architecture Review, but should not be considered a replacement. To schedule a call, please contact your Customer Success Manager.
2 Posit Workbench files on the system
As an Administrator of Posit Workbench, it is helpful to understand where the different files are located in the file system. Workbench places files in 3 main directories:
/etcfor configuration files/optfor R, Python, and Quarto installations/var/logfor log files
This diagram shows the types of file located in each of these directories:
.
├── etc
│ └── rstudio # Workbench configuration files
│ ├── rserver.conf
│ ├── rsession.conf
│ ├── jupyter.conf
│ ├── vscode.conf
│ ├── positron.conf
│ ├── launcher.conf
│ ├── repos.conf
│ ├── launcher.local.profiles.conf
│ ├── launcher.local.resources.conf
│ └── ...
├── opt
│ ├── python # Python installations from Posit provided pre-compiled binaries
│ │ ├── 3.12.x
│ │ │ └── bin
│ │ │ ├── python3
│ │ │ ├── jupyter
│ │ │ └── ...
│ │ ├── 3.11.x
│ │ │ └── bin
│ │ │ ├── python3
│ │ │ └── ...
│ │ └── ...
│ └── R # R installations from Posit provided pre-compiled binaries
│ ├── 4.4.x
│ │ └── bin
│ │ ├── R
│ │ ├── Rscript
│ │ └── ...
│ ├── 4.3.x
│ │ └── bin
│ │ ├── R
│ │ ├── Rscript
│ │ └── ...
│ └── ...
├── home # User home directories
│ ├── user1
│ ├── user2
│ └── ...
└── var
└── log
└── rstudio # Workbench log files
├── rstudio-server
│ ├── rserver.log
│ └── ...
└── launcher
├── rstudio-launcher.log
└── ...3 Cheatsheet
3.1 Managing Workbench
Terminal
# Check Workbench version
sudo rstudio-server version
# Edit configuration files (there are many configuration files,
# here are some of the most commonly edited ones, others are
# also in /etc/rstudio/)
sudo nano /etc/rstudio/rserver.conf
sudo nano /etc/rstudio/rsession.conf
sudo nano /etc/rstudio/launcher.conf
...3.2 Service Management
Terminal
## For rstudio-server
sudo systemctl status rstudio-server.service
sudo systemctl restart rstudio-server.service
sudo systemctl start rstudio-server.service
sudo systemctl stop rstudio-server.service
## For rstudio-launcher
sudo systemctl status rstudio-launcher.service
sudo systemctl restart rstudio-launcher.service
sudo systemctl start rstudio-launcher.service
sudo systemctl stop rstudio-launcher.service
## To fully restart Workbench (both rstudio-server and rstudio-launcher)
sudo systemctl stop rstudio-server.service rstudio-launcher.service
sudo systemctl start rstudio-launcher.service rstudio-server.service
sudo systemctl status rstudio-server.service rstudio-launcher.service 3.3 License Management
Terminal
# Check license status
sudo rstudio-server license-manager status4 Troubleshooting
If an issue is occurring that does not seem to be specific to a piece of content or dependent on server resources then there could be an issue related to the configuration of Workbench. These types of issues can often be resolved by searching the Workbench Administrator guide, however, if there are still questions the next step is to contact Posit Support.
4.1 Support Agreement
By purchasing Posit software you have access to Posit Support, which is outlined in our Support Agreement.
4.2 Filing a support ticket
You have access to an automated ticket and reporting service through which support requests are logged and ticket ID(s) issued within thirty minutes. For more information about submitting a support ticket review the instructions in the Open a support ticket section of the Posit Documentation.
The support team will need to get the output from the following command to help you troubleshoot the issue:
Terminal
sudo rstudio-server run-diagnostics