Issue Task Closed

#107044Site set settings path makes docker deployment and mounting very hard

Rozbeh Chiryai Sharahi 07/05/25, 19:02 updated 12/02/25, 14:38

Description

Hello,
Our project is just a sample, of course, and there are definitely sites that drive a completely different strategy where the following is no problem at all.

On our projects, we manage /config/sites/**/config.yaml files within git. However, with the new Site Sets, an additional /config/sites/**/settings.yaml is stored next to the config.yaml files. By the way, it’s awesome that you decided to separate those two files.

Therefore, I decided to have settings.yaml git-ignored, so we can, for instance, adapt settings on live like footerPageId=2134.

However, the fact that settings.yaml and config.yaml are stored within the same directory and the path is not configurable makes Docker deployments very difficult.

This is due to the following reasons:

1) We cannot simply mount the parent directory as config.yaml should be taken from git and is already baked into the Docker image at build time. Doing a mount would cause the config.yaml to be overridden by host volumes/directories, and all changes in git would have no effect anymore.

2) Even if we decide to only mount the settings.yaml (which is not that easy – mounting single files and managing file ownership at the same time is challenging, though possible), TYPO3 would run into an exception as it always deletes the settings.yaml once you revert the last settings configuration in the backend. This would lead to TYPO3 trying to delete a mounted file, which is not possible in Docker.

Not sure if I explained this well, but I hope so.

Possible solutions:

1) Maybe make settings.yaml file paths configurable? Looking at the core code, I don’t think this is manageable that quickly :) (SiteWrite)

2) Maybe remove or feature-flag that feature of deleting the settings.yaml once it is empty, so at least with some trouble it would be possible to mount the files

Kind regards

Reviews 3