After installing xdebug as extension to VS Code there is simple config you need to do to make it work with DrupalVM and debug. Create debug profile in standard VS code way and add this

Updating drupal commerce is still a bit messy, per docs here you need to run all of this to have any chance of updating

This are default mysql docksal settings.

This is just a standard .lando file recipe you can use to get you started

So file synching is a pain int he ass on MacOS so I made some tests with "wrk" tool to see what is what and how much request per second can each config handle. I started with install.php on D8 site as it is more about file and less about database and caching. Tool was used with this config (30s of requests) 

There are different ways in which we can run our PHPUnit tests. We can either run a full unit test, a test suite or one specific test as shown in following commands:

To run all the tests available from the custom modules directory:

For complex application, provisioning your box with the initial “vagrant up” command can take a long time. Fortunately, it’s not necessary to do this for every member of your team, on every computer that will be used for development. You can use the following command to create a filename.box file, which is the already provisioned box.

Some time ago I had some examples how to setup your local mysql for development
https://www.drupaldump.com/installing-percona-instead-mysql-checking-db-engines-tunning

Payment is specific entity in drupal commerce, usually it will be added by payment gateway module through checkout flow, but if you need to make some custom payments programmatically then you can do it in a following way, first you would need to get payment gateway object, so you can fetch proper info, after that you need to fill in paraparameters for new payment creation, depending on how you

Unlike shipments, each order has one billing profile, to change it programmatically we can first check it existence and then we can do the changes, it goes like this: