Feature #50131
closed
Feature #49988: Backport ApplicationContext from Flow
Load context specific configuration files
0%
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
Updated by Mathias Brodala almost 11 years ago
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.
Updated by Ingo Renner almost 11 years ago
came across some work Benni did: https://github.com/b13/t3ext-environment
Updated by Philipp Gampe almost 11 years ago
- 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.
Updated by Christian Kuhn over 10 years ago
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.
Updated by Steffen Müller over 10 years ago
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.
Updated by Christian Kuhn over 10 years ago
- Status changed from Accepted to Closed