To piggyback off of this, because I have the same issue, is there a way to change the configuration file through the Orthanc interface then, without having to restart Orthanc?
In my use-case, Orthanc runs on a restricted device, yet the data that the Orthanc serves is not private or is restricted, only the device hardware is. This means the end-user can not change configuration scripts or even restart Orthanc. It is then impossible to use a new DICOM viewer which was not added to the configuration file from the start.