With these steps you can get PhpStorm and Xdebug working together in DDEV or Lando. Read about how to enable and configure it in the official PhpStorm documentation. PhpStorm has built-in support for things like autocompletion, syntax highlighting, Drush, integration with the issue queue, and more. If you would like to know how to install Drupal or Acquia Drupal or XDebug please refer to the many articles already published.įor full documentation on using PhpStorm and Drupal, refer to the JetBrains documentation. Please notice that we have added the following environment variable to your docker-compose.This Article explains to you how to configure your PhpStorm to work with your local installation of Drupal and debug using XDebug. opt/projects/wpd/mysql:/var/lib/mysql networks: "3306:3306 " # I prefer to keep the ports available for external connections in the Development environment to be able to work with the database # from programs like e.g. MYSQL_ROOT_PASSWORD: mydbrootpassword #MYSQL_RANDOM_ROOT_PASSWORD: '1' # You can use this instead of the option right above if you do not want to be able login to MySQL under root MYSQL_DATABASE: mydbname MYSQL_USER: mydbuser MYSQL_PASSWORD: mydbpassword ports:
opt/projects/wpd/command: -default-authentication-plugin=mysql_native_password restart: always environment: VIRTUAL_HOST:, WORDPRESS_DB_HOST: db WORDPRESS_DB_NAME: mydbname WORDPRESS_DB_USER: mydbuser WORDPRESS_DB_PASSWORD: mydbpassword # Set the XDEBUG_CONFIG as described here: XDEBUG_CONFIG: remote_host=192.168.1.2 depends_on:
xdebug # a path to a directory containing a Dockerfile, or a url to a git repository ports: Container_name: wordpress-wpd restart: always build:ĭockerfile: Dockerfile # this line is actually redundant here - you need it only if you want to use some custom name for your Dockerfile context.
0 kommentar(er)
