Docksal and VSCode and Xdebug

To setup xdebug with docksal and VSCode there is not much to do. Make your debug profile with info like this

Xdebug with VSCode and DrupalVM

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

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

Docker/Vagrant on Mac speed tests

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) 

Running A PHPUnit Test

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:

Faster DrupalVM provisioning

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.