304 makes the docker images independent from the runtime config. However the solution is not complete because shanoir stores the actual pacs hostname in urls stored in dataset_file (which is problematic because this table is huge and we need to change this value each time we
In shanoir-old we used to rely on docker legacy link to avoid storing the hostname in the db (the urls were just http://pacs/...).
I would like to avoid legacy links (as they may disappear sometime in the future).
One possible solution would be to store a dummy url in the db, and generate the real url at runtime using the config keys dcm4chee-arc.{host,port.web,dicom-wado-uri.
eg: store the url as wado://?requestType... instead of http://dcm4chee-arc:8081/dcm4chee-arc/aets/DCM4CHEE/wado?requestType...
304 makes the docker images independent from the runtime config. However the solution is not complete because shanoir stores the actual pacs hostname in urls stored in
dataset_file
(which is problematic because this table is huge and we need to change this value each time wetake a snapshot for deploying in qualif/preprod)
Eg:
In shanoir-old we used to rely on docker legacy link to avoid storing the hostname in the db (the urls were just http://pacs/...).
I would like to avoid legacy links (as they may disappear sometime in the future).
One possible solution would be to store a dummy url in the db, and generate the real url at runtime using the config keys dcm4chee-arc.{host,port.web,dicom-wado-uri.
eg: store the url as
wado://?requestType...
instead ofhttp://dcm4chee-arc:8081/dcm4chee-arc/aets/DCM4CHEE/wado?requestType...