Open Akron opened 1 year ago
This issue is already relevant running different Kalamar instances. An example would be the configuration of queries and the vc of the guided tour which differ for different kalamar instances regarding to the available corpora. Right now, this is solved through adding an additional localization file and a change in the according app/xy.js files, but it would be far more elegant to use a dynamic approach her.
Currently, most client-side configurations (aside of plugins) require static inclusion before asset building. That's not a good approach for Docker and it's preferable to make these configuration also dynamic. A good idea would be to have them as a json file. For the moment, a dynamic JavaScript file is probably fine as well.