b266c0a86a
* feat: Add extensibility for tmtv and segmentation modes * Fixes for ordering issues on laod * Remove unnecessary reference lookup * Chane side panel timing to fix tests * PR comments - change how mode definitions get created * Improvements to mode customizations * Start organizing customizations * Misc fixes for a customization demo page * Security fixes * PR requested changes to naming
113 lines
5.1 KiB
JavaScript
113 lines
5.1 KiB
JavaScript
/** @type {AppTypes.Config} */
|
|
|
|
// Secure, minimal default configuration.
|
|
//
|
|
// This is what a plain production build with no APP_CONFIG produces, so it is
|
|
// deliberately locked down:
|
|
// - The local file data source (`dicomlocal`) and the runtime `?url=` sources
|
|
// (`dicomjson`, `dicomwebproxy`) are NOT enabled — they widen the attack
|
|
// surface of a default deployment.
|
|
// - `?customization=` URL loading is OFF: no `customizationUrlPrefixes` are
|
|
// configured, so any `?customization=` value is rejected (and aborts boot
|
|
// rather than silently loading).
|
|
// - `dangerouslyUseDynamicConfig` (the `configUrl` query parameter) is off.
|
|
//
|
|
// It does not need to "just work" untouched — point the data source below at
|
|
// your own DICOMweb server. For a fully-featured setup with every data source
|
|
// and customization loading enabled, see config/dev.js (local development) and
|
|
// config/netlify.js (the public demo deploy).
|
|
window.config = {
|
|
name: 'config/default.js',
|
|
routerBasename: null,
|
|
// whiteLabeling: {},
|
|
extensions: [],
|
|
modes: [],
|
|
customizationService: {},
|
|
|
|
// --- URL-driven customizations (?customization=) ----------------------------
|
|
// OFF by default. To allow loading customization data files from the URL, set
|
|
// `customizationUrlPrefixes` to a map of allowed prefixes. The `default` prefix
|
|
// (no slashes) is used for values with no leading slash; every other prefix
|
|
// must start AND end with a slash and is matched against the leading
|
|
// `/segment/` of the value. Files are fetched and parsed as JSONC data — they
|
|
// are never executed. Example (left disabled here on purpose):
|
|
//
|
|
// customizationUrlPrefixes: {
|
|
// default: './customizations/', // ?customization=tools/ctPresets
|
|
// '/remote/': 'https://cdn.example.com/ohif-custom/', // ?customization=/remote/siteA
|
|
// },
|
|
// ----------------------------------------------------------------------------
|
|
showStudyList: true,
|
|
// some windows systems have issues with more than 3 web workers
|
|
maxNumberOfWebWorkers: 3,
|
|
// below flag is for performance reasons, but it might not work for all servers
|
|
showWarningMessageForCrossOrigin: true,
|
|
showCPUFallbackMessage: true,
|
|
showLoadingIndicator: true,
|
|
experimentalStudyBrowserSort: false,
|
|
strictZSpacingForVolumeViewport: true,
|
|
groupEnabledModesFirst: true,
|
|
allowMultiSelectExport: false,
|
|
maxNumRequests: {
|
|
interaction: 100,
|
|
thumbnail: 5,
|
|
// Prefetch number is dependent on the http protocol. For http 2 or
|
|
// above, the number of requests can be go a lot higher.
|
|
prefetch: 25,
|
|
},
|
|
showErrorDetails: 'always', // 'always', 'dev', 'production'
|
|
// `dangerouslyUseDynamicConfig` (load configuration from a `configUrl` query
|
|
// parameter) is intentionally left OFF in the secure default build. See
|
|
// config/dev.js for the documented shape.
|
|
defaultDataSourceName: 'ohif',
|
|
dataSources: [
|
|
{
|
|
// Read-only public demo server. Replace with your own DICOMweb server.
|
|
namespace: '@ohif/extension-default.dataSourcesModule.dicomweb',
|
|
sourceName: 'ohif',
|
|
configuration: {
|
|
friendlyName: 'AWS S3 Static wado server',
|
|
name: 'aws',
|
|
wadoUriRoot: 'https://d14fa38qiwhyfd.cloudfront.net/dicomweb',
|
|
qidoRoot: 'https://d14fa38qiwhyfd.cloudfront.net/dicomweb',
|
|
wadoRoot: 'https://d14fa38qiwhyfd.cloudfront.net/dicomweb',
|
|
qidoSupportsIncludeField: false,
|
|
imageRendering: 'wadors',
|
|
thumbnailRendering: 'thumbnail',
|
|
thumbnailRequestStrategy: 'fetch',
|
|
enableStudyLazyLoad: true,
|
|
supportsFuzzyMatching: true,
|
|
supportsWildcard: true,
|
|
staticWado: true,
|
|
// Multiframe SEG loads fetch the whole instance as a single Part 10
|
|
// object by default and wait for it: the per-frame endpoint is
|
|
// efficient, but SEG frames are so small and numerous that one bulk
|
|
// fetch beats hundreds of tiny requests. Per-frame loading is the
|
|
// exception — set loadMultiframeAsPart10: false here to force it.
|
|
singlepart: 'bulkdata,video',
|
|
bulkDataURI: {
|
|
enabled: true,
|
|
relativeResolution: 'studies',
|
|
transform: url => url.replace('/pixeldata.mp4', '/rendered'),
|
|
},
|
|
omitQuotationForMultipartRequest: true,
|
|
},
|
|
},
|
|
|
|
// The following data sources are intentionally NOT enabled in the secure
|
|
// default because they broaden the attack surface of a default deployment.
|
|
// Enable them only in a deployment you control (see config/dev.js):
|
|
// - dicomlocal: loads DICOM files from the user's machine.
|
|
// - dicomjson: loads metadata from an arbitrary `?url=` (gate with
|
|
// `dangerouslyAllowedOriginsForAuthenticatedEnvironments`).
|
|
// - dicomwebproxy: delegating proxy driven by `?url=`.
|
|
],
|
|
httpErrorHandler: error => {
|
|
// This is 429 when rejected from the public idc sandbox too often.
|
|
console.warn(error.status);
|
|
|
|
// Could use services manager here to bring up a dialog/modal if needed.
|
|
console.warn('test, navigate to https://ohif.org/');
|
|
},
|
|
};
|