Tutorial: Deployment in PhpStorm

What is specified in the Connection tab?

Select the directory where the project files will be uploaded. In our case, this is the /Applications/MAMP/htdocs local folder. You can either type the path manually, or press Shift+Enter.)

What is specified in the Mappings tab?

Next, switch to the Mappings tab. By default, the Local path field contains the path to the project root. However, you can select any other directory within your project tree. Let's assume the default value.

In the Deployment path field (which is by default empty), specify the folder on your server, where PhpStorm will upload data from the folder specified in the Local path field: in this example, it's myApp. This path is specified relative to the web server root folder, which is /Applications/MAMP/htdocs.

Finally, accept the default / value for Web path:

After you apply the changes, the server is ready to use.

Uploading

First, let's upload one of the files to the remote server.

In the Project tool window, right-click a file you want to upload. In our case, let it be the header.php file . From the context menu, choose Upload to MyRemoteServer, and see the upload results.

You can also upload contents of each directory within your project. For example, right-click the parent directory of the , namely, src header.php and choose Deployment | Upload to MyRemoteServer from the context menu. We now have the entire directory uploaded to the server:

Comparing remote and local versions

There is a local and a remote copy of the header.php file , and they are identical. Let's modify the local version.

Now we've changed the local version. Let's make sure PhpStorm knows about these changes. To do that, go to the Remote host tool window tool window, and right-click . From the context menu, choose Compare with Local Version. PhpStorm opens the differences viewer.

Downloading

In the Remote host tool window tool window, right-click the file , and choose Download from here in the context menu. PhpStorm shows a warning:

Click Yes:

You can also download an entire directory, if it has been previously uploaded to the server. For example, if you click the parent pub directory and choose the same command, all nested files will be downloaded from the server.

Defining a server as default

A deployment server is considered default if its settings apply by default during automatic upload of changed files. To define a deployment server as the default one, follow these steps:

Enabling automatic upload

As soon as the default server is set, you can make upload to this server automatic. This can be done in the following two ways:

• Open the deployment Options

  (Settings/Preferences | Deployment | Options or Tools | Deployment | Options from the main menu), and in the Upload changed files automatically to the default server field choose Always, or On explicit save action. The difference between these two choices is explained in the field description.

• In the main menu, select Tools | Deployment | Automatic upload. Note that automatic upload in this case is performed in the Always mode.

It is worth noting that the Always mode is not recommended for deploying to production: incomplete code can be uploaded while developing, potentially breaking the production application.