Feature summary
Allow CXServer to support dynamic configuration per host by introducing hooks at key points in the code. This will enable fetching configuration dynamically instead of relying solely on static YAML files. User can still use static configuration, but can also set a flag to inject dynamic one per host.
Use case(s)
We running multi systems, each have its own different languages, each uses different MT api keys, etc. We need a way to apply different configurations per system and per host dynamically. The proposed solution is to introduce hooks at specific points in the code, allowing configurations to be retrieved dynamically based on the host.
Benefits
- Enables more granular control over configurations per host without modifying static files.
- Reduces operational overhead and manual configuration updates.
- Allows for greater flexibility in multi-system, multi-host environments.
We are willing to implement this feature ourselves, including writing the necessary code. Our question is whether such a change would be acceptable to the project maintainers.