Anyone who only ever runs tests and CLI commands in the terminal loses valuable seconds on every cycle. Run configurations in PhpStorm turn the green play button into a real tool, with a Docker interpreter, Xdebug integration and compound runs for complex workflows.
A PhpStorm that struggles through hundreds of modules with default configuration is not a productivity tool. Indexing excludes, heap configuration, sensible scopes, and inspection profiles tuned to the project type make the difference between an IDE that helps and one that slows you down.
PhpStorm ships with a full database client, complete with SQL autocompletion, EXPLAIN PLAN visualization, schema diff and query analysis. Anyone who knows these tools no longer needs to open TablePlus, DBeaver or Sequel Pro.
PhpStorm can do more than just display code: start Docker Compose services, activate Xdebug in the container, run Magento CLI commands, and use the remote interpreter for autocompletion, once you know what really belongs together and what is better left in the terminal.
PhpStorm on a Magento 2 project with hundreds of thousands of vendor files can feel like a sluggish tool. The reason is almost always the same: too many files in the index, too little heap memory, too many active plugins. With systematic diagnosis the problem can be fixed within an hour.
Magento 2 ships its own test infrastructure that differs substantially from a standard PHPUnit project. If you want to run integration tests directly from PHPStorm, see coverage reports in the IDE, and debug individual test methods with a single click, you need specific configuration, which this article covers in full.
Xdebug with Docker is not a one-click setup: host.docker.internal, port 9003, path mappings, the correct xdebug.mode, and PHPStorm server configuration all have to line up. This article systematically puts every piece into the right position, for stable breakpoints in Magento 2 and other PHP projects.
A freshly installed PHPStorm without a checklist costs hours: wrong interpreter, too much indexed vendor bulk, no Xdebug, no run configurations. This checklist covers all the critical settings, in the order that matters most for Docker Magento projects.
Using PHPUnit in PhpStorm is trivial when PHP is installed locally. With Docker interpreters, Magento-specific bootstrap files and integration tests that require a running database, the configuration becomes more complex. This guide shows how to solve each of these cases cleanly.
PhpStorm's remote host integration with automatic SFTP upload is powerful, and dangerous if used the wrong way. This article explains which scenarios the feature is built for, where its limits lie, and at what project size a Git-based CI/CD pipeline becomes the clearly better choice.