{"id":19960,"date":"2016-06-21T15:02:00","date_gmt":"2016-06-21T15:02:00","guid":{"rendered":"https:\/\/blog.jetbrains.com\/phpstorm\/?p=10268"},"modified":"2016-06-30T14:17:39","modified_gmt":"2016-06-30T14:17:39","slug":"debugging-vvv-vagrant-setup-with-phpstorm","status":"publish","type":"phpstorm","link":"https:\/\/blog.jetbrains.com\/pt-br\/phpstorm\/2016\/06\/debugging-vvv-vagrant-setup-with-phpstorm","title":{"rendered":"Debugging VVV Vagrant Setup With PhpStorm"},"content":{"rendered":"

It started with a Tweet:<\/p>\n

\n

Who do i know that uses PHPstorm with VVV and XDebug? I need some guidance on getting things setup.<\/p>\n

\u2014 Andrew Woods (@awoods) June 21, 2016<\/a><\/p><\/blockquote>\n

 <\/p>\n

Recently we’ve made a lot of changes to debugging in PhpStorm to try and make the process as simple as possible. So I decided to blog about not only\u00a0how to get debugging working, but the process I used to figure out exactly what needed to be changed.<\/p>\n

<\/p>\n

Varying Vagrant Vagrants<\/a> is a Vagrant setup designed to make working with WordPress as easy as possible. It has various versions of WordPress running under separate URLs. For this exercise, I installed the plugins that the documentation recommended, and then cloned the repository, and used `vagrant up` to bring the box up and run its provisioners.<\/p>\n

The good news is this was really simple\u00a0and allowed me to hit the\u00a0current stable version URL at `http:\/\/local.wordpress.dev` quickly and easily to see my working WordPress install.<\/p>\n

The first thing I did was to open the project in\u00a0PhpStorm. I’d cloned VVV into the `www` directory in my user’s home folder under the name `vvv`. I didn’t want to confuse everything by opening the various different versions of WordPress in one project, so I just used PhpStorm’s\u00a0Open Directory<\/em> option to open a project from `~\/www\/vvv\/www\/wordpress-default`. This gave me a project open that linked directly to the webroot of the\u00a0`http:\/\/local.wordpress.dev` URL. It’s important to consider these factors when you are deciding what to make your projects root to make mapping paths easier — more on this later.<\/p>\n

At this point, I have no idea how this vagrant box is configured. Is it using\u00a0Apache? Is it using\u00a0Nginx and PHP-FPM? Who knows! It’s really not that important, but generally, the first thing I do once I’ve opened the project is to\u00a0tell PhpStorm which PHP install I’m going to use. Doing this straight away tends to make potential problems less likely to appear further down the line.<\/p>\n

The settings we want are found in the Preferences pane under\u00a0Languages & Frameworks<\/em> then\u00a0PHP\u00a0<\/em>(if you are as lazy as I am, you can use CMD\/CTRL+SHIFT+A to search actions and then type `interp`<\/em> to go right there). We’ll need to define a new interpreter, so click the […]<\/em> button next to the\u00a0Interpreter:<\/em> drop down, to be taken to the Interpreters <\/em>management screen.<\/p>\n

\"Interpreters<\/p>\n

You can see that currently I only have my global local PHP install configured, so we’ll need to create a new interpreter for this Vagrant box to tell the project to use it. It’s relatively straightforward to create an interpreter for a vagrant machine; I used the following steps:<\/p>\n