Move context configuration defaults to package
Currently we deliver certain configuration defaults for the Testing and Production context in the global Configuration/ directories. This is annoying, because it's really defaults of the package, not of the distribution and whenever the options / defaults change in FLOW3, everybody needs to manually update the defaults in their distribution's Configuration/ directory (such as in the TYPO3 distribution).
Additionally it gives a bad user experience: The global Configuration/ directory is meant for configuration options added by the user. These directories should actually be empty with a fresh checked out FLOW3 or TYPO3 distribution.
Solution: Move the defaults into the package's Configuration directory and add support for that into the configuration management.
Updated by Robert Lemke over 11 years ago
For the time being (until we need something more sophisticated), this feature is now implemented as follows:
- Only the FLOW3 package can have context directories in its Configuration dir
- Currently the Configuration Manager only looks for settings in that additional directory - other configuration types are ignored