Improved configuration TYPO3 for environments

TYPO3 Association Community Budget Ideas 2024 Q4
1

By Łukasz Uznański

What is your idea about?
Improve out of the box TYPO3 configuration for multiple environments. Add documentation on best practices for management of configuration files and credentials.

What do you want to achieve by the end of Q4 2024?

Patch to the core with new functionality that can handle TYPO3_CONTEXT for loading environment specific settings. Also split loading of configuration for different kinds of environments based on environment variables. It won’t break the current implementation of AdditionalConfiguration.

Our proposed ordering of configuration loading:

  1. DefaultConfiguration
  2. LocalConfiguration (settings.php)
  3. Environment context based files - this is new
  4. Special environment file - this is new (you can configure path for it)
  5. AdditionalConfiguration (additional.php)

Add documentation on best practices for your environment configuration and credentials management.

What is the potential impact of your idea for the overall goal?

This budget idea aims to streamline development, improve security, and ease deployment across environments, benefiting the TYPO3 community by making management of configurations more efficient and scalable.

Which budget do you need for your idea?

5.000 Euro

Please note: After the start of the voting we can not change the idea description nor the idea outcome. If this idea is selected by the members, it must be archived as described.

2 Likes
2

See also discussion Improved TYPO3 configuration for environments

3

hmm sounds like normal credential management and config management.
I think it helps to look what options exists.
Like:

  • gitops way - dont save credentials in git but you can use credential references with operators like external secrets
  • multiple environments - using symfony/dotenv component
1 Like
4

Reading all that I would suggest to repharase the budget idee to work on a written “concept” first. And getting thoughts and opionon from more people.

The current form would make it either useles for some confiuration workflow or needs more in the chain. Beside that it assumps things (TYPO3 CONTECT HARD SET earlier than that versus reality where a lot of projects sets the TYPO3_CONTEXT soley in additional.php

3 Likes