[Config] Config files deployment
#8 Updated by Michał Kłobukowski over 1 year ago
1. This should be done in the deploy process all automated and it should be part of the code because these configs should be able to be replicated on install from the package. ie for customers who do their own install from packages and we don't have access to.
#9 Updated by Michał Kłobukowski over 1 year ago
2. For me these are two different scenarios. The config.json configures the instance so this should be done on install. However the vocabulary.json is more dynamic and it needs to be possible to change it between Installations.
In our case the vocabulary.json is generated every couple of hours from an API and replaces the previous one
In a way the vocabulary.json is like an external API itself. One possible way could be to configure the URL of the vocabulary.json in the config.json which would allow us to use a rest API directly instead of a static json file
#10 Updated by Tom Clegg over 1 year ago
configure the URL of the vocabulary.json in the config.json
This sounds like the way to go. It might be a local path, or any URL that allows cross-origin requests.
We might also want to provide an example file "example-vocabulary.json" in the workbench package, and refer to that in the example config comments/documentation.