Task #7479
Move context configuration defaults to package
| Status: | Resolved | Start date: | ||
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Robert Lemke | % Done: | 100% |
|
| Category: | Configuration | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 9 | |||
| Sprint: | Has patch: | |||
| PHP Version: | Complexity: |
Description
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.
Associated revisions
[+FEATURE] FLOW3 (Configuration): The ConfigurationManager now supports context directories in the FLOW3 package's Configuration directory. This allows us to deliver the FLOW3 distribution (and other distributions) with a virtually empty global Configuration directory. Resolves #7479
[~TASK] FLOW3 Base Distribution: Removed the global context configurations.
[+FEATURE] FLOW3 (Configuration): The ConfigurationManager now supports context directories in the FLOW3 package's Configuration directory. This allows us to deliver the FLOW3 distribution (and other distributions) with a virtually empty global Configuration directory. Resolves #7479
[~TASK] FLOW3 Base Distribution: Removed the global context configurations.
History
#1 Updated by Robert Lemke over 5 years ago
- Status changed from New to Accepted
- Assigned To set to Robert Lemke
- Target version set to 1.0 alpha 9
#2 Updated by Robert Lemke over 5 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
#3 Updated by Robert Lemke over 5 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r4230.