Skip to main content
Configure domains only after DNS resolves to the Dokploy server. Compose-service domain changes require a redeployment before the proxy labels take effect.

​
Domain routes

Do not create public routes for postgres, oie-postgres, orthanc-postgres, Orthanc Explorer, raw DICOMweb, mock-analyzer, or mock-modality.
1

Create DNS records

Create the required A or AAAA records and wait for them to resolve from an external network.
2

Add the HMIS domain

In the Dokploy Compose service, route {{HMIS_DOMAIN}} to service app, port 80, with HTTPS and automatic certificate management enabled.
3

Add optional protected domains

Add OHIF and temporary OIE browser routes only when those services are enabled. Apply the access controls before sharing the URL.
4

Redeploy and verify TLS

Redeploy the Compose service, open each approved URL, confirm the expected certificate and redirect, and verify /up on the HMIS origin.

​
OIE Administrator client

The browser route terminates HTTPS at Dokploy and forwards to OIE HTTP port 8080. The desktop Administrator client uses OIE’s separate HTTPS management port 8443 and cannot use that browser proxy route. Keep 8443 bound to loopback. Use a VPN or SSH tunnel:
Then connect the Administrator client to https://127.0.0.1:8443.

​
Persistent volumes

Do not rename, delete, or recreate volumes during a release. Before moving storage, stop writers and capture a consistent database-and-volume backup.

​
Storage controls

  • Alert at 80% disk utilization and escalate at 90%.
  • Keep at least 25% free space for builds, database maintenance, and restore staging.
  • Separate imaging storage when study growth threatens the system disk.
  • Encrypt host disks and backup repositories according to hospital policy.
  • Restrict backup and Docker-volume access to named administrators.
  • Do not treat a VPS snapshot as the only database backup.
Continue with the first deployment.