Issue Feature Under Review Orphaned

#107814settings.yaml does not support context-specific configuration based on ApplicationContext

Stefan Froemken 10/22/25, 20:05 updated 02/13/26, 12:20

Description

Hi,

Currently, TYPO3 supports baseVariants within the config.yaml file, allowing context-based configuration by evaluating conditions such as the ApplicationContext.

However, this concept does not extend to settings.yaml, site sets, or site definitions.

This limitation makes it impossible to define site settings that differ between environments (e.g. Development, Production, or sub-contexts like Development/dev-1) without duplicating or overriding configurations manually.

What about following structure:

Development/settings.yaml
Development/dev-1.settings.yaml
Production/settings.yaml

TYPO3 could automatically merge or override these configurations based on the current ApplicationContext.
This would align with TYPO3’s existing baseVariants concept but offer a cleaner and more maintainable approach, avoiding repetitive “condition” declarations for each setting.

Maybe that issue is something for EPIC: https://forge.typo3.org/issues/103034

Stefan

Reviews 1

History 518

  1. Timo Webler commented <span data-processor="relativetime" data-value="2025-10-23T05:42:59+00:00" > 10/23/25, 05:42 </span>

    Maybe we can find a solution that fits here and for #105819