Configuration Management
Configuration management helps teams reuse proven settings across projects. In TTModeler, there are two recommended approaches depending on your goal:
- Reuse the configuration of one specific project as a starting point for another project.
- Maintain one centrally managed configuration and update projects through merge operations.
Reuse a Project-Specific Configuration
Use this approach when you want to create a new project based on a known project configuration.
- Open the source project in TTModeler.
- Download its configuration via Project > Download Configuration.
- Depending on platform and storage setup, open the configuration file first via File > Open, if not already added to the list of configuration files.
- Return to the home page.
- Start a new project and use the downloaded configuration as the project base.
This is a practical way to clone the setup of an existing project without copying the full project content.
Best Practice: Central Configuration + Merge
For long-term maintainability, use one central configuration file as the single source of truth.
Recommended operating model:
- Maintain configuration changes in the central configuration file.
- Do not manually evolve each project configuration independently.
- Update projects by merging the central configuration into each project configuration.
For details on the merge process, see Merge Configuration.
Important Considerations
Take extra care when reusing a project-specific configuration or merging central updates into project configurations:
- Projects may contain new protocols, components, or other project-specific entries. In a central configuration, these might be missing. In a project-specific configuration, these entries are existing but might not be needed.
- During merge decisions, verify that project-specific extensions are kept where needed.
- Review merge requests carefully before applying them, especially for changed or deleted entries.