AppCode
 
2022.2
Shortcuts: macOS
Get AppCode
You are viewing the documentation for an earlier version of AppCode.
  1. Reference
  2. AppCode Preferences
  3. Tools
  4. SSH Configurations

SSH Configurations

Last modified: 17 March 2022

AppCode | Preferences | Tools | SSH Configurations

⌃ ⌥ S the Preferences icon

Use this page to create SSH configurations, which can be used for configuring remote interpreters, connecting to SFTP deployment servers, and launching SSH sessions.

the Add button Add Insert

Create a new SSH configuration.

the Remove button Delete Alt+Delete

Remove the selected SSH configuration.

note

This will affect the configured remote interpreters, SFTP deployment servers, and SSH sessions that depend on this configuration.

the Copy button Copy Ctrl+D

Create a copy of the selected SSH configuration.

the Rename button Rename ⇧ F6

Rename the selected SSH configuration.

SSH configuration settings

Visible only for this project

Restrict this SSH configuration to the current project. The configuration will not be available in other projects. AppCode stores such configurations in the project's .idea directory, which you can share between team members in a VCS.

By default, this option is disabled and AppCode stores the SHH configuration in the IDE configuration directory. In this case, you can use this configuration in any project when working from the current instance of AppCode.

Host

Specify the hostname of the server to connect to. The default value is localhost.

Username

Specify the username for authentication to the server.

Port

Specify the remote port number to connect to. The default value is 22 (the standard TCP port for SSH).

Local port

Specify the local port number from which you want to forward the connection. There is no default value, which means AppCode dynamically selects the port number.

Authentication type

Select the client authentication method:

  • Password: Authenticate with the specified password and remember it if necessary.

  • Key pair: Use SSH authentication with a key pair (OpenSSH or PuTTY). Specify the location of the private key file and the corresponding authentication passphrase. The public key should be on the remote server. Remember the passphrase if necessary.

  • OpenSSH config and authentication agent: Use a credentials helper application that manages your SSH keys, such as ssh-agent.

    For example, see the following tutorial: Generating a new SSH key and adding it to the ssh-agent.

Parse config file ~/.ssh/config

Read the OpenSSH client-side configuration file for any options not specified in the SSH configuration for the corresponding host.

This option is available only for Password and Key pair authentication types. With OpenSSH config and authentication agent, AppCode reads the OpenSSH config file in any case.

Test Connection

Try to connect with the current SSH configuration settings.

Connection Parameters

Send keep-alive messages every

Send regular packets to keep the SSH connection active. Without regular messages, the remote server might close the connection. Set the message period in seconds.

Strict host key checking

Specify how to handle new and changed host keys.

  • Yes: Never add new host keys to the user's known_hosts file and never allow connections to hosts with changed host keys.

  • Accept New: Always add new host keys to the user's known_hosts file but never allow connections to hosts with changed host keys.

  • No: Always add new host keys to the user's known_hosts file and allow connections to hosts with changed host keys.

  • Ask: Add new host keys to the user's known_hosts file only after confirmation and never allow connections to hosts with changed host keys. This is the default behavior.

Hash hosts in knownhosts file

Store new host records in hash format.