RubyMine 2017.2 Help

Configuring Remote Interpreters via SSH

Prerequisites

  • A ssh server should run on a remote host, since RubyMine runs remote interpreter via ssh-session.
  • If you want to copy your sources to a remote computer, create a deployment configuration, as described in the section Creating a Remote Server Configuration.

Configuring remote Ruby interpreter via SSH credentials

To configure a remote Ruby interpreter via SSH credentials

  1. In the Ruby SDK and Gems page of the Settings/Preferences dialog box, click /help/img/idea/2017.2/add.png.
  2. From the drop-down list, choose New remote... .
    /help/img/idea/2017.2/rm_remote_interpreter_choose.png

    The dialog box Configure Remote Ruby Interpreter opens.

  3. In the dialog box Configure Remote Ruby Interpreter, click the radio-button SSH credentials:
    /help/img/idea/2017.2/rm_configure_remote_interpreter.png

    Mind the suggestion to install RSync to speed up the download process. For details, refer to the section Using RSync for Downloading Remote Gems.

  4. In the Configure Remote Ruby Interpreter dialog box, fill in the server information (host, port, etc.)

    Note the Auth type field. It suggests the following options: Password, Key pair and Authentication agent. If you choose one of the first two options, you should have to enter your password or passphrase. However, the last option allows you to use the authentication agents ssh-agent or Pageant.

  5. The Ruby interpreter path field displays the path to the desired Ruby executable. You can accept default, or specify a different one.
  6. Click OK in the Configure Remote Ruby Interpreter dialog box.
  7. Back in the Ruby SDK and Gems page, if necessary, configure the path mappings:
    1. Click /help/img/idea/2017.2/edit_path_mapping_icon.png:
      /help/img/idea/2017.2/rm_edit_path_mapping.png
    2. In the dialog box that opens add (/help/img/idea/2017.2/add.png) or delete (/help/img/idea/2017.2/delete.png) path mappings as desired.

See Also

Language and Framework-Specific Guidelines:

Last modified: 21 July 2017