Core

Ehm, we already have application context in 6.2.
You can query them in TS too.

What do you mean with this ticket?

Markus Klein wrote:

Ehm, we already have application context in 6.2.
You can query them in TS too.

What do you mean with this ticket?

I mean being able to have an unlimited amount of configuration files like this:

typo3conf/ProductionConfiguration.php
typo3conf/DevelopmentConfiguration.php
typo3conf/Development/VirtualMachineConfiguration.php
typo3conf/LocalConfiguration.php

If I am in Production context, only the ProductionConfiguration.php is loaded.
If I am in Development, only the DevelopmentConfiguration.php is loaded.
If I am in Development/VirtualMachine, DevelopmentConfiguration.php and VirtualMachineConfiguration.php are loaded.
The LocalConfiguration.php is loaded in any case.

For a formal description see TYPO3 Flow Documentation: Configuration

I think I don't have to mention the vast advantages of a configuration setup like this. ;-)

At least you can easily emulate this already with the AdditionalConfiguration.php file.
Just implement a simple include there.

Markus Klein wrote:

At least you can easily emulate this already with the AdditionalConfiguration.php file.
Just implement a simple include there.

Yes, I know and I already use this file for various purposes. But this issue is about supporting this kind of configuration setup out of the box and properly just like TYPO3 Flow.

Markus Klein wrote:

At least you can easily emulate this already with the AdditionalConfiguration.php file.
Just implement a simple include there.

As can be seen in #57289 it is actually not possible to fully override the LocalConfiguration.php using the AdditionalConfiguration.php in any case.

For the reference there is at least the environment extension which implements something like this.