Skip to content


Posit End User License Agreement

This page includes instructions for downloading Posit professional products. Download and/or use of these products is governed under the terms of the Posit End User License Agreement. By downloading, you agree to the terms posted there.

These instructions describe how to install Posit Package Manager on a single Linux server. For alternative installation instructions, see our Install Posit Professional Products overview. Depending on your environment, additional steps may be required to install Package Manager.

Multi-server installation

If you would like to install Package Manager on multiple Linux servers, use these instructions to install Package Manager on each server and then continue to the Multi-Server Installation procedures.

If you've already installed Package Manager, we recommend reviewing our Quick Start documentation to help administrators configure Package Manager for your organization's specific use cases.


Please review and complete the following before proceeding:

For air-gapped or offline installations, review these additional requirements:


Step 1. Download and install#

Download and install the server application version 2024.04.4-35 (see the Signed Build section below to verify the signature of the package):

sudo apt update
sudo apt install gdebi-core
curl -fO
sudo gdebi rstudio-pm_2024.04.4-35_amd64.deb
sudo apt update
sudo apt install gdebi-core
curl -fO
sudo gdebi rstudio-pm_2024.04.4-35_amd64.deb
curl -fO
sudo dnf install rstudio-pm-2024.04.4-35.x86_64.rpm
curl -fO
sudo dnf install rstudio-pm-2024.04.4-35.x86_64.rpm
curl -fO
sudo yum install rstudio-pm-2024.04.4-35.x86_64.rpm
sudo zypper refresh
curl -fO
sudo zypper install rstudio-pm-2024.04.4-35.x86_64.rpm
sudo zypper refresh
curl -fO
sudo zypper install rstudio-pm-2024.04.4-35.x86_64.rpm


These commands install the product into /opt/rstudio-pm. See the Manual Installation for Minimal Root Use section to install into a non-default location or to perform a non-root install.

Signed Build#

The Package Manager installer is signed with a key belonging to Posit. If you'd like to know more about the benefits of using signed builds, see the Posit Signed Builds page.

For product builds released after 7/25/23 (including new and patched builds), use the "Post 7/25/2023" key. For builds released prior to 7/25/23, use the "Pre 7/25/2023" key.

Obtain the key:

We have two ways to obtain the key:

  • Obtain the public key from our website and save it into a file (e.g., posit.key).
  • Obtain the key from a GnuPG keyserver using the following commands:

    gpg --keyserver --search-keys 51C0B5BB19F92D60
    gpg --armor --export 51C0B5BB19F92D60 > posit.key
    gpg --keyserver --recv-keys 3F32EE77E331692F
    gpg --armor --export 3F32EE77E331692F > posit.key

Once you have obtained the key, you need to import it into the set of keys RPM uses to validate package signatures, after which you can validate the package signature using the rpm command:

# Import the key into the set of keys RPM uses to validate package signatures
sudo rpm --import posit.key

Validate the Package Manager installer executing the following commands:

dpkg-sig --verify rstudio-pm_2024.04.4-35_amd64.deb
rpm -K rstudio-pm-2024.04.4-35.x86_64.rpm

Step 2. Initial Configuration#

By default, Package Manager settings are controlled by a configuration file located at /etc/rstudio-pm/rstudio-pm.gcfg.

If Package Manager is served from a subdirectory like /packagemanager/, you must configure the Server.Address setting for some features to work, such as PyPI package serving and the Server API documentation.

Server.Address should be the public URL for this server in the format of http(s)://[HOST:PORT]. If Package Manager is deployed behind an HTTP proxy, this should be the URL for Package Manager in terms of that proxy.

Otherwise, Server.Address is optional and may be left unset.

; /etc/rstudio-pm/rstudio-pm.gcfg
Address =

; Or if served at a subdirectory like /packagemanager/
;Address =

There are many other options you may want to configure now or in the future, such as:

Example configuration file

An example configuration file that includes all of the available configuration settings along with their defaults is installed at /etc/rstudio-pm/rstudio-pm.gcfg.defaults.

Step 3. Activate license#

To verify the status of your license:

/opt/rstudio-pm/bin/license-manager status

If you have a license key, then activate the license by replacing LICENSE_KEY with the value of your license key:

/opt/rstudio-pm/bin/license-manager activate LICENSE_KEY

For full details and information about offline activation, see the Licensing page.

Step 4. Restart Package Manager#

After updating the configuration file and activating the license, you must restart the Package Manager service:


Most configuration setting changes can also be updated by taking the Package Manager service offline and bringing it back online. For more information, see the Online and Offline Modes page.

To restart the Package Manager service, run the following commands:

sudo systemctl stop rstudio-pm
sudo systemctl start rstudio-pm

Package Manager supports the HUP signal when:

  • Making licensing changes.
  • Activating a new license.

Step 5. Verify installation#

There are two ways to verify a successful Package Manager installation:

  • View the Package Manager Web UI.
  • The Admin Command-line interface.

View the Package Manager Web UI#

As a user, you can view Package Manager in a web browser, which provides a user-friendly interface for viewing information about packages, package READMEs, metrics, etc. See the User Guide for additional information.

To view Package Manager in a web browser:

  1. Open a web browser.
  2. Navigate to Package Manager by following http(s)://<port> (the default port is 4242).

Once you navigate to the Package Manager URL, the Package Manager Welcome page displays. For any administrative changes, use the CLI.

The Admin Command-line Interface#

Package Manager is administered through a command-line interface (CLI) which administrators can use to:

  • Create repositories and sources.
  • Setup sync schedules for CRAN sources.

To invoke the Admin CLI, run: /opt/rstudio-pm/bin/rspm list

If you aren't able to access the Admin CLI, then verify that your user is a member of the rstudio-pm group by doing the following:

  1. Run the following to add USER to the rstudio-pm group (replace <USER> with your username):

    sudo usermod -aG rstudio-pm <USER>
  2. Close the terminal or SSH session.

  3. Start a new session and run the groups command. This enumerates the groups that the current user is a member of.
  4. Confirm that rstudio-pm is listed.
  5. Run the command:

    /opt/rstudio-pm/bin/rspm list


You can select a different group to grant access to the Admin CLI. For more information, see the Changing RunAs User page.

Optional downloads#

There are two additional executables that are optional depending on the intended installation:

  • Standalone CLI: Used to remotely manage the server with actions like adding packages or uploading binaries.
  • Offline Downloader: Used to download remote assets to initialize or upgrade air-gapped servers.

Download and install the standalone CLI#

The standalone rspm CLI can be used for several actions such as adding packages or uploading binaries remotely (for more information, see the Quick Start page):

curl -o rspm -f${RSPM_SERVER_VERSION}
chmod +x rspm
curl -o rspm -f${RSPM_SERVER_VERSION}
chmod +x rspm

Ensure compatibility by setting the RSPM_SERVER_VERSION environment variable to the server version. The server version can be found by running the following commands on a running Package Manager server:

$ rspm --version
Posit Package Manager Server Version: 2024.04.4-35; ...

Download and install offline downloader#


The rspm-offline-downloader utility is required for air-gapped installations of Package Manager to function correctly (see the Air-Gapped Package Manager section):

curl -o rspm-offline-downloader -f
chmod +x rspm-offline-downloader
curl -o rspm-offline-downloader -f
chmod +x rspm-offline-downloader

For a list of changes, see the Package Manager: Offline Downloader release notes.