1

I'm trying to have a config setup for a multisite, so that I have following config directories:

  • default - common config
  • dev - split for dev environment
  • local - split for local environment
  • <site> - split for a site

When I'm working on a local copy of the site, this means I have local and <site> splits active at the same time. I've experienced, that all the configuration apart from that blaclisted in local was then exported (when running drush cex) to the <site> split, so default directory is empty. How can I override this behavior, so that <site> split would contain only specified graylisted configuration?

4
  • drush csex <site> maybe? – leymannx Oct 26 '20 at 19:51
  • 1
    Thanks @leymannx, it looks like it works, after I manually moved the config to the default config directory. I still would like to know, if there's any automated solution using ordinary cex. – Miloš Kroulík Oct 26 '20 at 19:59
  • Not sure 🤔. For me this setup seems to be a bit error-prone. I prefer each site having its completely own config and syncing shared features with the Features module during development. drupal.stackexchange.com/a/297630/15055 – leymannx Oct 26 '20 at 20:08
  • Hmm, I evaluated features module as an alternative, but abandoned the idea, because config_split seems to be much more used solution, so I expected better support possibilities. – Miloš Kroulík Oct 26 '20 at 20:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.