Handle non-activated services on site install

In our developer workflow we install the site continuously during development, as a health check of the code base. One of the problems we have in this workflow is when we declare a service that belongs to a module that is not activated yet during the install, like Memcache module. In our developer workflow we install the site continuously during development, as a health check of the code base. One of the problems we have in this workflow is when we declare a service that belongs to a module that is not activated yet during the install, like Memcache module. This is what a site needs normally in settings.php,  $settings['memcache']['servers'] = ['localhost:11211' => 'default']; $settings['memcache']['bins'] = ['default' => 'default']; $settings['memcache']['key_prefix'] = 'foo_bar'; $settings['cache']['default'] = 'cache.backend.memcache'; This works perfect to add on a runnings site when the module is activated… Read More