2.2 KiB
Deployment
The OHIF Viewer can be embedded in other web applications via it's packaged script source, or served up as a stand-alone PWA (progressive web application) by building and hosting a collection of static assets. In either case, you will need to configure your instance of the Viewer so that it can connect to your data source (the database or PACS that provides the data your Viewer will display).
Overview
Our goal is to make deployment as simple and painless as possible; however, there is an inherent amount of complexity in customizing, optimizing, and deploying web applications. If you find yourself a little lost, please don't hesitate to reach out for help
Deployment Scenarios
Embedded Viewer
The quickest and easiest way to get the OHIF Viewer up and running is to embed it into an existing web application. It allows us to forego a "build step", and add a powerful medical imaging viewer to an existing web page using only a few include tags.
- Read more about it here: Embedded Viewer
- And check out our live demo on CodeSandbox
{% include "./_embedded-viewer-diagram.md" %}
Stand-alone Viewer
Deploying the OHIF Viewer as a stand-alone web application provides many benefits, but comes at the cost of time and complexity. Some benefits include:
Today:
- Leverage extensions to drop-in powerful new features
- Add routes and customize the viewer's workflow
- Finer control over styling and whitelabeling
In the future:
- The ability to package the viewer for App Store distribution
- Leverage
service-workersfor offline support and speed benefits from caching
Hosted Static Assets
...
Docker
...