The first run at start often fails because Blaze is not ready yet. A
daily run keeps the load low on large stores; the Refresh button in the
UI re-validates on demand.
Adds the ITCC blaze data-model validator next to the uploader. It fetches
from the local Blaze over the compose network (BLAZE_URL), while the
resource links in its UI point at the browser-facing route
(PUBLIC_BLAZE_URL = Blaze's traefik /itcc-localdatamanagement mapping) —
the two URLs differ because everything external is relative to ${HOST}.
The UI is exposed like the uploader's: /itcc-validator with basic auth
(auth middleware) and strip-prefix.
* sites moved to etc itcc.comf
* mainzelliste test
* volume
* fix image
* db name chaged
* ingest component test
* clean up
* maizelliste env db
* test server ip
* beam sockets
* teswt socket and task
* secure db and ml
* refactor and patient endpoints
* partner id
* new refactor and encription key generation
* db deleted
* keyset to var/
Pierre Delpy
Skiba, Jan
Jan
Martin Jurk