...
What tools do you have to do that?
| Expand | ||
|---|---|---|
| ||
This is good Custom Fields are a good method for configuring details which apply for to a single specific component. You can create custom fields in the Translator config.json file and include default values that are stored in source control. Custom fields entered in the Component Card are encrypted and stored locally in the working directory. See Custom Fields. |
| Expand | ||
|---|---|---|
| ||
These are not too bad good for dealing with properties which need to be defined across the server. Environment variables are stored locally in the working directory in IguanaEnv.txt. |
...
| Expand | ||
|---|---|---|
| ||
It’s a good idea to reduce the number of configuration parameters if you can. Less is more. If you find you never change a setting, consider removing that setting from your list of configuration parameters. Try and simplify things. See What are bottlenecks and why do they matter? For instance say you need to configure retry settings for your HL7 listeners - why not come up with some universal settings that ‘just work’ at 100% of your sites without needing any special configuration - does not seem like a better idea than engaging in busy work? |
...