...
What tools do you have to do that?
| Expand | ||
|---|---|---|
| ||
Custom Fields are a good method for configuring details which apply for to a 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 Component Configuration Files. |
| Expand | ||
|---|---|---|
| ||
These Environment Variables are good for dealing with properties which need to be defined across the server. Environment variables They are stored locally in the your working directory in IguanaEnv.txt. See Environment Variables Configuration File. |
| Expand | ||
|---|---|---|
| ||
I wrote a small library to allow one to load a JSON file from another component when you supply the name of the component and the name of the file. This might be helpful: CONFIG Library |
| 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? Bottlenecks 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? |
...