Feature #61066

Configuration per application context

Added by Mathias Brodala about 5 years ago. Updated over 1 year ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
System/Bootstrap/Configuration
Target version:
-
Start date:
2014-08-19
Due date:
% Done:

0%

PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

TYPO3 Flow allows for different configuration per application context (even subcontexts). The same should be supported in CMS, too.


Related issues

Related to TYPO3 Core - Bug #57289: Respect additional configuration file for silent configuration upgrade Closed 2014-03-25

History

#1 Updated by Markus Klein about 5 years ago

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

What do you mean with this ticket?

#2 Updated by Mathias Brodala about 5 years ago

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. ;-)

#3 Updated by Markus Klein about 5 years ago

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

#4 Updated by Mathias Brodala about 5 years ago

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.

#5 Updated by Mathias Brodala almost 5 years ago

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.

#6 Updated by Mathias Schreiber over 4 years ago

  • Target version changed from 7.0 to 7.1 (Cleanup)

#7 Updated by Mathias Brodala over 4 years ago

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

#8 Updated by Markus Klein over 4 years ago

  • Target version changed from 7.1 (Cleanup) to 7.4 (Backend)

#9 Updated by Susanne Moog about 4 years ago

  • Target version changed from 7.4 (Backend) to 7.5

#10 Updated by Benni Mack almost 4 years ago

  • Target version changed from 7.5 to 8 LTS

#11 Updated by Riccardo De Contardi over 2 years ago

  • Target version changed from 8 LTS to 9.0

#12 Updated by Susanne Moog almost 2 years ago

  • Category changed from Miscellaneous to System/Bootstrap/Configuration

#13 Updated by Susanne Moog over 1 year ago

  • Target version deleted (9.0)

Also available in: Atom PDF