othmane/ohif-viewer
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Transition to configuration

Browse Source
This commit is contained in:
dannyrb 2019-04-30 10:39:24 -04:00
parent b5cac7191d
commit 0909ab7c53
2 changed files with 30 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/latest/SUMMARY.md
View File

@ -36,14 +36,16 @@
- [Stand-alone](deployment/index.md#stand-alone-viewer) - [Stand-alone](deployment/index.md#stand-alone-viewer)
- [Data]() - [Data]()
- Recipes - Recipes
- [Embedding the Viewer](deployment/recipes/embedded-viewer.md) - Script Include
- [Build for Production](deployment/recipes/build-for-production.md) - [Embedding the Viewer](deployment/recipes/embedded-viewer.md)
- [PWA: Static]() - Stand-Alone
- [PWA: Docker]() - [Build for Production](deployment/recipes/build-for-production.md)
- [PWA: Nginx + Orthanc]() - [Static]()
- [PWA: Nginx + dcm4chee]() - [Docker]()
- [PWA: Nginx + DICOMCloud]() - [Nginx + Orthanc]()
- [PWA: User Access Control]() - [Nginx + dcm4chee]()
- [Nginx + DICOMCloud]()
- [User Access Control]()
--- ---

22
docs/latest/deployment/recipes/build-for-production.md
View File

@ -4,7 +4,7 @@
> ["Getting Started" Guide](/essentials/getting-started.md), you can skip ahead > ["Getting Started" Guide](/essentials/getting-started.md), you can skip ahead
> to [Configuration](#configuration) > to [Configuration](#configuration)
## Overview? ## Overview
### Build Machine Requirements ### Build Machine Requirements
@ -57,7 +57,10 @@ build
└── ... └── ...
``` ```
These files can be hosted using By default, the build output will connect to OHIF's publicly accessible PACS. If
this is your first time setting up the OHIF Viewer, it is recommended that you
test with these default settings. After testing, you can find instructions on
how to configure the project for your own imaging archive below.
### Configuration ### Configuration
@ -73,6 +76,21 @@ These files can be hosted using
TODO: List of recipes TODO: List of recipes
### Testing Build Output Locally
A quick way to test your build output locally is to spin up a small webserver.
You can do this by running the following commands in the `build/` output
directory:
```js
// Install http-server as a globally available package
yarn global add http-server
// Serve the files in our current directory
// Accessible at: `http://localhost:8080`
http-server
```
### Automating Builds and Deployments ### Automating Builds and Deployments
If you found setting up your environmnent and running all of these steps to be a If you found setting up your environmnent and running all of these steps to be a