Feature #50131
closed
Feature #49988: Backport ApplicationContext from Flow
Load context specific configuration files
Added by Ingo Renner about 11 years ago.
Updated almost 11 years ago.
Description
Extracted from issue #39441
Depending on context load additional configuration, overwriting LocalConfiguration.php settings.
Proposed solution:
Store additional configuration in typo3conf/{ContextName}ContextConfiguration.php. Check whether such a file exists for the current context, then load the file and overwrite/merge the settings with those from LocalConfiguration.php
How are sub-contexts handled in this case? Strictly speaking one would have to create subdirectories if the context is e.g. Production/Server/Main.
- Status changed from New to Accepted
IMHO Subcontext should be handled by subdirectories. The file should be called Configuration.php
or LocalConfiguration.php
, otherwise it gets confusing.
Please check how Flow does this. We should stay in sync as much as possible.
This can probably already achieved with AdditionalConfiguration.php: This way admin has full control about it and we don't need to take care about things like sub context files or the like.
I agree with Christan:
- A default preset for development and production context can now be set in the install tool.
- Customer specific settings can be added to AdditionalConfiguration or even put into specific files using require().
I'd suggest to close this issue.
- Status changed from Accepted to Closed
Also available in: Atom
PDF