Skip to content

andylinton/ohif-dcm4chee

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 
 
 

Repository files navigation

OHIF-dcm4chee

This project combines the excellent PACS/VNA dcm4chee along with OHIF as a viewer. Integration with traefik as reverse proxy, using DNS challenge to provide SSL certificates for a given domain. Dozzle is used to monitor logs The intention is to run these services on an internal network, not open to the internet.

Steps before starting:

  • ensure your local DNS points your domain name (eg example.com) and wildcard (eg *.example.com, OR each individual subdomain) to you docker server.
  • rename .env.development to .env
  • set DOCKER_HOSTNAME in .env, set other environment variables as desired.
  • ensure you have access to DNS provider for domain name and traefik can communicate for DNS-01 challenge, generate API tokens. This example uses Dreamhost
  • customise ./config/app-config-example.js and rename to app-config.js - set <arc_subdomain>.<docker_host>, <keycloak_subdomain>.<docker_host> and <ohif_subdomain>.<docker_host> to your chosen address for each service (eg pacs.example.com)
  • set docker secrets
    • traefik basic auth: sudo htpasswd -cBb <project directory>/secrets/basic_auth_credentials HTTP_USERNAME HTTP_PASSWORD
    • replace HTTP_USERNAME with desired username, HTTP_PASSWORD with your password
    • run sudo nano <project directory>/secrets/dreamhost_api_key (replace dreamhost_api_key with the relevant name for your DNS provider, see https://doc.traefik.io/traefik/https/acme/#providers)
    • set appropriate environment variable name in traefik container for your API key (eg CF_API_EMAIL_FILE for cloudflare, DREAMHOST_API_KEY_FILE for dreamhost)
  • run the following command, and wait until ldap initialisation finished, then Ctrl-C (may not be necessary, but on my system the project did not start cleanly unless LDAP was initialised first)
docker compose up ldap
  • run
docker compose up -d
  • log in to keycloak (https://<keycloak_subdomain.docker_host>/admin/dcm4che/console), remove port numbers in dcm4chee-rs and dcm4chee-ui client URLS (for default credentials see dcm4chee-arc-light docs
  • In keycloak admin, create ohif-viewer client (can import /config/ohif-viewer-example.json after customising URLs)
  • Log out, then log in to dcm4chee (https://<arc_subdomain.docker_host>/dcm4chee-arc/ui2), check that initial view loads successfully
  • finally trial logging in to OHIF (https//<ohif_subdomain.docker_host>)

Note: takes a while for keycloak to spin up the first boot, be patient.

Resources:

About

Docker deployment of OHIF and dcm4chee-arc-light

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published