Architect Server

Architect has built-in functionality that allows you to connect to an R session running on a remote server. Once connected to a remote R session, users have seamless access to all the Architect's local features, such as integrated data visualization tools and streamlined code evaluation.

Below we give instructions for installing Architect Server and configuring connection to a remote R console.

Server Installation

If you want to install Architect Server from our Ubuntu package repository, follow the steps below:

Step One: Connect to the server

Connect to the server via the terminal

Step Two: Add our GPG-key

Inside the terminal, type:

gpg --keyserver --recv-key 18F3EEF7

Then type:

gpg -a --export 18F3EEF7 | sudo apt-key add -

It should say 'OK'.

Step Three: Edit your sources.list

In the terminal, type:

sudo nano /etc/apt/sources.list

Go to the end of the file and add the code corresponding to your operating system:

For Ubuntu 14.04:

deb trusty main

For Ubuntu 16.04:

deb xenial main

Now save and close the file (in nano: Ctrl+O and Ctrl+X).

Finally, run:

sudo apt-get install architect-server

Now you're ready to configure your remote R console within Architect.

Alternative instructions

Alternatively, .deb and .rpm package files are available for Architect Server on our downloads page.


Download the .deb file, then type in the terminal:

dpkg -i XXX.deb

where 'XXX.deb' is the name of the downloaded .deb file.


Download the .rpm file, then type in the terminal:

rpm -i XXX.rpm

where 'XXX.rpm' is the name of the downloaded .rpm file.

Client Configuration

Inside Architect, type Ctrl + 3 to pull up the Quick Search menu, then search for 'Run Configurations'. Click on 'R Remote Console' in the left menu, then click the 'new configuration' button () to define a new run configuration.

Then, fill in the address of your server and your credentials. A sample completed configuration looks as follows.

We recommend checking the 'Tunnel connections to R engine through SSH' box, which secures the connection and does not require opening an extra port on the firewall. Note that Architect Server assumes that users have credentials to access the remote server over SSH.

Once configured, launch the newly created configuration choosing it via the configuration selector black arrow ().

In the above screenshot, we've named this configuration 'my_generic_connection'. Naming a remote session allows users to have multiple uniquely named remote configurations defined. Above, the sessions 'my_generic_connection' and 'my_generic_connection2' could be run concurrently.

We can go one step further and label a configuration as a 'favorite' in the Common tab.

This places the selected configuration in a favorites list at the top of the run configuations dropdown menu ().

Remote R Help

Browsing an R help directory on a remote server is possible via the Remote Systems Explorer (RSE) eclipse plugin.

  1. Install the RSE plugin from the eclipse marketplace: Help > Eclipse Marketplace...

  2. Open the Remote Systems view : Window > Show View > Other... then under Remote Systems select Remote Systems.

  3. Create a new connection by clicking the 'new connection' button () and use the dialog to configure the remote endpoint. If the remote server is a *nix based system, we suggest to select use ssh only.

  4. Next, configure a remote R environment for your remote R console.

  5. follow steps 1-5 on installing different versions of R
  6. on step 5, instead use the dropdown next to the Add... button to select Add Remote.
  7. configure the remote in the following way:

    where HOST should correspond to the host in the RSE connection

  8. Launch your remote R console. After the index has finished updating ([INFO] Updating the R environment index started), restart the remote R console. The remote help view should now be working.