IntelliJ IDEA distinguishes among in-place, local, and remote servers, however the meaning of these terms in the context of IntelliJ IDEA slightly differs from their common meaning:
- An in-place server is a server whose document root is the parent of the project root, either immediate or not. In other words, the Web server is running on your computer, your project is under its document root, and you do your development directly on the server.
- A local server is a server that is running in a local or a mounted folder and whose document root is NOT the parent of the project root.
- A remote server is a server on another computer (remote host).
For more information about possible configuration of the production and development environment and working with servers from IntelliJ IDEA, see Working with Web Servers: Copying Files.
IntelliJ IDEA controls interaction with Web servers through server access configurations. Anytime you are going to use a server, you need to define a server access configurations, no matter whether your server is on a remote host or on your machine.
A server access configuration defines:
- The server type (in-place, local, or remote).
- The computer (host) where the server is running. For in-place and local servers, IntelliJ IDEA presupposes that it is the current computer where your project is.
- The server access configuration root: the highest folder in the server hierarchy that can be accessed through the server configuration.
- The URL address to access the server configuration root . Both the HTTP and the HTTPS protocols are supported.
- The protocol to transfer the data through.
- Correspondence between local (project) folders, destination folders on the server, and URL addresses to access the data on the server. This correspondence is called mapping.
You can define as many configurations as necessary, thus enabling flexible switching between upload/download setups.
Synchronization with servers, uploading, downloading, and managing files on them are provided via the Remote Hosts Access bundled plugin, which is by default enabled. If not, activate it in the Plugins page of the Settings dialog box. For details, see Enabling and Disabling Plugins.
In this part: