Question about drush cr

Related: https://www.drupal.org/forum/support/module-development-and-code-questio... →

To add to that, make sure that drush and the webserver use the same redis prefix, which you can lock down through settings.php, then a drush cr should work fine.

That said, our build scripts actually do include a ./vendor/bin/drush ev "\Drupal::service('redis.factory')->getClient()->flushAll()" because it cleans out redis, so it doesn't have to slowly get rid of invalidated cache items over time, but we can only do that because we know that each drupal site has its own isolated redis instance.