The JetBrains Client's version is always equal to the version of the backend IDE. For example, if there is the PhpStorm 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). Additionally, the advanced code intelligence implemented on the PhpStorm 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. 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 PhpStorm. To better understand bits and pieces of this architecture, you need to get familiar with the following definitions: Server The thin client, for example, a laptop, connects to the host and transparently provides full access to all IDE features. The remote host is a physical (Linux) or virtual machine hosting the source code and running a headless PhpStorm instance. Remote development lets you use the IDE interface on a thin client while having a powerful remote host to check out and load your project, index, analyze, build, run, debug, and test your code.
0 Comments
Leave a Reply. |