Vagrant

It started with a Tweet: Who do i know that uses PHPstorm with VVV and XDebug? I need some guidance on getting things setup. — Andrew Woods (@awoods) June 21, 2016   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 how to get debugging working, but the process I used to figure out exact

More and more PHP developers are shifting to a workflow where they use PhpStorm on their local machine and run and debug their PHP applications on a remote server or Vagrant machine. Which is great! Every project we're working on would have its dedicated, virtual development machine and we easily share the project configuration and development environment with our team. Even version it through sou

Support for PHP remote interpreters has been introduced in PhpStorm 8 EAP. It lets us use a PHP interpreter over SSH installed on any remote environment, to run/debug application and run testing tools remotely. Using a remote interpreter instead of a local one gives us an opportunity to get advantages of a PHP interpreter installed in a production-like environment (be it a physical server, a vi

With PhpStorm 7, we introduced built-in support for working with Vagrant, a tool which helps to create reproducible development environments. These scripted virtual machines can then be shared using a simple script, instead of having to share a full-blown virtual machine. These scripts can even be added to source control so virtual machine configurations can be versioned. The latest PhpStorm 7.

The latest version of the PhpStorm 7 EAP comes with Vagrant integration! Vagrant is a tool which helps us create reproducible development environments. By scripting a virtual machine, Vagrant allows us to share a development machine by sharing a simple script. Other developers can then launch an identical machine by running the vagrant up command. Or by doing this from within the IDE! Once the