Problem/Motivation

Setting up a split directory structure for a multilingual multisite is somewhat multi-confusing. I'm testing both the Collection and Folder approach and here's what I have.

On the documentation page Split Directory Structure, one can read this:

Do **NOT** put configuration directories inside of each other. In particular the split folder **MUST NOT** be inside of the sync directory.

And the examples given are somewhat ambiguous, not 100% clear to me.

  1. Question: can I adopt any of the 2 approaches illustrated below?
  2. Question: which is the recommended one for my use case?

MULTISITE SETUPS (multilingual)

Using Collection storage

config
├── default
│  └── language
│      └── en
├── site-1
│  └── split
│      ├── dev
│      ├── prod
│      └── stage
├── site-2
│  └── split
│      ├── dev
│      ├── prod
│      └── stage
└── site-3
    └── split
        ├── dev
        ├── prod
        └── stage

 

Using Folder storage

config
├── splits
│  ├── site-1
│  │  └── dev
│  ├── site-2
│  │  └── stage
│  └── site-3
│      └── prod
├── default
│  └── language
│      └── en
├── site-1
│  └── split
│      ├── prod
│      └── stage
├── site-2
│  └── split
│      ├── dev
│      └── prod
└── site-3
    └── split
        ├── dev
        └── stage

Comments

bisonbleu created an issue. See original summary.

bisonbleu’s picture

Issue summary: View changes
bisonbleu’s picture

Issue summary: View changes
bisonbleu’s picture

Issue summary: View changes

Note that the 'Collection' storage structure is automatically provided as is by config_split.module. While the 'Folder' storage structure is the one I created based on my understanding of the documentation.

The documentation seems to suggest that the 'Collection' storage structure will not work ?

bisonbleu’s picture

Issue summary: View changes

Answering my own question.

It turns that the directory structures displayed in the summary are "dirty", they contain artifacts from numerous experiments and as such do not clearly represent the storage options. Let's clean up the first one which uses the Collection storage.

Below is what use to be in the issue summary and it is wrong/incorrect. The summary now displays the correct directory structure.

config
├── default
├── site-1
│  ├── language
│  │  └── en
│  └── split
│      ├── dev
│      │  └── language
│      │      └── en
│      └── prod
│          └── language
│              └── en
├── site-2
│  ├── language
│  │  └── en
│  └── split
│      ├── dev
│      │  └── language
│      │      └── en
│      └── prod
│          └── language
│              └── en
├── site-x
│  ├── language…
bisonbleu’s picture

Issue summary: View changes

Answering my own question - part #2.

The directory structures displayed in the summary are "dirty", they contain artifacts from numerous experiments and as such do not clearly represent the storage options. Let's clean up the second one which uses the Folder storage using this pattern: ../config/splits/site-x/server.

Below is what use to be in the issue summary and it is wrong/incorrect. The summary now displays the correct directory structure.

config
├── default
├── splits
│  ├── site-1
│  │  ├── dev
│  │  │  └── language
│  │  │      └── en
│  │  ├── prod
│  │  │  └── language
│  │  │      └── en
│  │  └── stg
│  ├── site-2
│  │  ├── dev
│  │  │  └── language
│  │  │      └── en
│  │  ├── prod
│  │  │  └── language
│  │  │      └── en
│  │  └── stg
│  ├── site-x
│  │  ├── dev
│  │  │  └── language
│  │  │      └── en
│  │  ├── prod
│  │  │  └── language
│  │  │      └── en
│  │  └── stg
├── site-1
│  └── language
│      └── en
├── site-2
│  └── language
│      └── en
├── site-x
│  └── language
│      └── en
bisonbleu’s picture

Assigned: Unassigned » bisonbleu
Issue summary: View changes
Status: Active » Fixed

My best answer in the current context

I ended up using the Collection storage option because it felt safer since the directory structure is automatically handled by the module.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

bisonbleu’s picture

Issue summary: View changes
bircher’s picture

Status: Fixed » Closed (works as designed)

Hi
I am glad you found your solution!