

Keep in mind that the connection is bound to a specific project. In case of backend previously installed by JetBrains Gateway, the default path is /home/your_system_user/.cache/JetBrains/RemoteDev/dist/.įor more information and available parameters, run remote-dev-server.sh -help The main script to run a remote IDE is remote-dev-server.sh, located in the bin subdirectory of your unpacked IDE. In short, the process can be described as "Start backend project in remote IDE -> select one of the connection links generated by the backend -> open it on your local machine". Use this approach if your company has a custom orchestration or in case your remote IDE starts automatically on its side. It works the same way as from JetBrains Gateway. If you already have CLion installed on your remote server, you can launch it manually and connect to the remote project started in that IDE.
#CLION REMOTE INSTALL#
Server-to-client flow: when an organization first sets up a remote headless server, obtains a link (customized or not) which then can be used by you on Client (for example, your laptop) to connect to the available server.Ĭlient-to-server flow: when you set up and install the remote server from the Client UI using the SSH or other connection.Ĭonnect to a remote project at manually launched remote IDE (Server-to-client flow) There are two types of main workflows available in remote development with the thin client: Moreover, JetBrains Gateway is responsible for holding the connection, handling reconnects (with or without UI consent), and indicating the status information about the current connections. It is the JetBrains Gateway process that configures and establishes a connection to Server (SSH or port forwarding or any other custom connection) and launches JetBrains Client against the opened connection or a port. JetBrains Gateway is responsible for the following tasks:Īllowing you to set up a remote connection to any kind of remote backend you haveĮxploring existing recent remote projectsĬonnecting to either the new or recent projectsĭownloading JetBrains Client of the appropriate version from the indicated storage After you request an environment in JetBrains Gateway, it launches JetBrains Client that is specific to that environment. It runs on Client, and lets you create new remote environments or connect to the existing ones. This is an entry point for remote development. JetBrains Client's version is always equal to the version of the backen IDE. For example, if there is the CLion 2021.3 version installed on Client, the downloaded and just launched JetBrains Client will import its settings, so the remote development experience will be personalized for you. JetBrains Client is based on the IntelliJ platform, therefore it imports any local IDE settings found on the local machine (Client).
#CLION REMOTE CODE#
Additionally, the advanced code intelligence implemented on the CLion server is presented in a way that looks as if it is running locally. In contrast to remote-desktop solutions, JetBrains Client has an advanced editor based on the JetBrains Rider’s RD protocol, which makes typing feel instant. It gets connected to the IDE backend and gives you the ability to do remote development as if it is local. This is a thin client you see after you launch JetBrains Gateway and establish a connection to a remote server. This is the same executable as you might currently be running for your JetBrains IDE. It is run as a server process, and therefore has no visible user interface - it’s headless. This is a compatible JetBrains IDE running on the server.
#CLION REMOTE WINDOWS#
Requirements: macOS, Linux, Windows IDE Backend However, there are no restrictions for clients specifications. This is a physical machine used by you to connect to the server and provide a thin client for working. Requirements: Linux (macOS and Windows are coming later) Client This is a physical or virtual machine to host the source code and run the headless CLion. To better understand bits and pieces of this architecture, you need to get familiar with the following definitions: Server
#CLION REMOTE FULL#
The SSH connection allows you to quickly connect to the remote server and take full advantage of CLion features. Remote development with the thin client lets you use a remote server as a development environment. Overview of remote development with the thin client
