#107814settings.yaml does not support context-specific configuration based on ApplicationContext
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
Related issues 2
History 518
-
Garvin Hicking changed Related to #103034 <span data-processor="relativetime" data-value="2025-10-23T05:23:12+00:00" > 10/23/25, 05:23 </span>
-
Timo Webler changed Duplicates #105819 <span data-processor="relativetime" data-value="2025-10-23T05:30:11+00:00" > 10/23/25, 05:30 </span>
-
Timo Webler changed
Duplicates #105819<span data-processor="relativetime" data-value="2025-10-23T05:30:26+00:00" > 10/23/25, 05:30 </span> -
Timo Webler changed Related to #105819 <span data-processor="relativetime" data-value="2025-10-23T05:30:29+00:00" > 10/23/25, 05:30 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 92259 status
NewUnder Review <span data-processor="relativetime" data-value="2026-01-07T15:37:55+00:00" > 01/07/26, 15:37 </span> -
Gerrit Code Review pushed patch set 5 for main to change 92259 <span data-processor="relativetime" data-value="2026-01-07T15:55:33+00:00" > 01/07/26, 15:55 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 92259 <span data-processor="relativetime" data-value="2026-01-07T16:16:13+00:00" > 01/07/26, 16:16 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 92259 <span data-processor="relativetime" data-value="2026-01-07T16:16:29+00:00" > 01/07/26, 16:16 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 92259 <span data-processor="relativetime" data-value="2026-01-07T16:16:48+00:00" > 01/07/26, 16:16 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 92259 <span data-processor="relativetime" data-value="2026-01-08T09:21:02+00:00" > 01/08/26, 09:21 </span>
-
Gerrit Code Review pushed patch set 10 for main to change 92259 <span data-processor="relativetime" data-value="2026-01-08T09:22:23+00:00" > 01/08/26, 09:22 </span>
-
Gerrit Code Review pushed patch set 11 for main to change 92259 <span data-processor="relativetime" data-value="2026-01-08T09:55:56+00:00" > 01/08/26, 09:55 </span>
-
Gerrit Code Review pushed patch set 12 for main to change 92259 <span data-processor="relativetime" data-value="2026-01-29T15:17:21+00:00" > 01/29/26, 15:17 </span>
-
Gerrit Code Review pushed patch set 13 for main to change 92259 <span data-processor="relativetime" data-value="2026-02-09T08:44:01+00:00" > 02/09/26, 08:44 </span>
-
Gerrit Code Review pushed patch set 14 for main to change 92259 <span data-processor="relativetime" data-value="2026-02-09T08:57:43+00:00" > 02/09/26, 08:57 </span>
-
Gerrit Code Review pushed patch set 15 for main to change 92259 <span data-processor="relativetime" data-value="2026-02-12T09:52:29+00:00" > 02/12/26, 09:52 </span>
-
Gerrit Code Review pushed patch set 16 for main to change 92259 <span data-processor="relativetime" data-value="2026-02-13T12:20:04+00:00" > 02/13/26, 12:20 </span>
Maybe we can find a solution that fits here and for #105819