Vmext demo is relying on the files in the config folder. Changing these configs will be deployed to DKE and trigger different evaluation pipelines on tpami.wmflabs.org
I think the easiest and most logical solution is to ignore the properties files. Now the file is still in the repo but user changes to will not end up on our server.
Vmext demo is relying on the files in the config folder. Changing these configs will be deployed to DKE and trigger different evaluation pipelines on tpami.wmflabs.org
I deactivated DKE deploy as an emergency solution. After vacation, this must be fixed asap. Especially because it may have other side effects. Luckily, vmext-demo imports its own config file so that the new config file format is not an issue for now: https://github.com/ag-gipp/srv-dke01/blob/6d551b71f393ad878b0fa5ecf40c1fbd386cb3ec/docker/docker-compose.yml#L125