So before we made an setup for rsyslog and some advanced log output that can be read by datadog (or others).

In this post I will show you how to setup monitor, alerting and drupal syslog module. So let's first start with drupal syslog, I usually set this setup for syslog format

Basic setup

So I will assume you installed syslog and have some default config running for it with syslog_facility set to log_local0. With that lets assume you are using rsyslog and you have config for it in

/etc/rsyslog.conf

which could have all config in this file or separated config files that are included with

Do this on your local or virtual enviroment, depending where do you want to have it

mkdir ~/drush10
cd ~/drush10
composer require "drush/drush:10.*"

this will install drush10 to that directory and now you just need to add alias

To add multiple ssh keys to your system, you need to edit config file ~/.ssh/config and put lines like below, this will also help store password for your ssh in keychain and use agent forwarding so you can use your keys on virtual machines like vagrant

drush ev 'cache_set("foo", "bar", "cache");'
drush ev '$x = new MemCacheDrupal("cache"); print_r($x->get("foo"));'

snippet to check if memcache is working.

To have shared history between sessions in terminal I use this settings so that history is appended to each new window I open

To setup SSL on DrupalVM with self-signed certificate you need a few commands and to change config, choose a place where you will store your certificates and then run first

sudo openssl genrsa -out "devcert.key" 2048

then do the

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

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