7/6/2023 0 Comments Magento 2 devdocs deployment![]() ![]() ![]() ![]() Change to a directory to which the Magento file system owner has write access.Įnter the following command in a terminal to log in to your project:.Log in to your local development system, or switch to, the Magento file system owner.To add Xdebug, we recommend creating a branch to work in and add the files. To configure Xdebug, you need to do the following:įor configuring on Pro plan Staging and Production, you need to enter a ticket for Staging and Production. You can locate the information through the Project Web Interface or your spreadsheet. To run and use Xdebug, you will need the environment’s SSH URL. For Pro plan Staging and Production, we include additional instructions for Xdebug on those environments. You will need to pull code to your local development environment to perform debugging. Remember, all Magento Commerce Cloud environments are read-only. Once configured, you can debug CLI commands, web requests, code. To push these settings to Pro plan Staging and Production environments, you must enter a ticket. After editing, you can push the Git changes across all Starter environments and Pro Integration environments to enable Xdebug. You will configure settings in the file. To set up Xdebug, you need to configure a file in your Git repo, configure your IDE PhpStorm, and set up port forwarding. Please see the vendor documentation for those applications for further configuration information. The following sections detail how to configure Xdebug and PhpStorm to work locally with settings in your environments. We recommend using Xdebug for your PHP debugging. For the latest supported documentation, see. This archived documentation is not supported. ![]()
0 Comments
Leave a Reply. |