Closed hackermd closed 3 years ago
@igoroctaviano do you know why the check fails? Should these tests even run in this fork?
You want to use a configuration like this:
window.config = {
path: "/slim",
servers: [
{
id: "idc",
url: "", // URL of DICOMweb proxy
write: false
}
],
renderer:
{
retrieveRendered: false
},
annotations: [ ],
disableWorklist: true,
disableAnnotationTools: true
};
@igoroctaviano do you know why the check fails? Should these tests even run in this fork?
Actually, the deploy failed because it's missing the firebase service acc.
Error: Input required and not supplied: firebaseServiceAccount
maybe something specific to IDC pipeline? @wlongabaugh
@igoroctaviano do you know why the check fails? Should these tests even run in this fork?
Actually, the deploy failed because it's missing the firebase service acc.
Error: Input required and not supplied: firebaseServiceAccount
maybe something specific to IDC pipeline? @wlongabaugh
I think we only configured the application/action for the main slim repo, but not for the IDC fork.
@igoroctaviano do you know why the check fails? Should these tests even run in this fork?
Actually, the deploy failed because it's missing the firebase service acc.
Error: Input required and not supplied: firebaseServiceAccount
maybe something specific to IDC pipeline? @wlongabaughI think we only configured the application/action for the main slim repo, but not for the IDC fork.
I think thats right, we need to migrate the firebase config files.
The viewer is built and deployed to a static bucket using our CircleCI build process. The firebase config files should not be triggered in IDC.
@wlongabaugh this PR adds the features recently introduced into the master branch of upstream slim repo. Note that the new features to take effect, changes to the configuration will be necessary.
I'd recommend creating a separate
idc.js
configuration file instead of modifying thelocal.js
(the latter is intended to work with theDockerfile
anddocker-compose.yml
configurations).