Prerequisites

Required DNS names

Create only the records needed by the enabled services. Point each record to the Dokploy server before requesting certificates.

Placeholder	Purpose	Required
`{{HMIS_DOMAIN}}`	Main HMIS user and API endpoint	Yes
`{{STAGING_HMIS_DOMAIN}}`	Staging HMIS endpoint	Yes
`{{OHIF_DOMAIN}}`	Protected imaging viewer	When radiology is enabled
`{{OIE_ADMIN_DOMAIN}}`	Temporary protected OIE browser administration	When OIE is enabled

Network access

Port	Source	Destination	Policy
22/TCP	Approved administrator IPs or VPN	Server	Restrict; disable password login after key verification
80/TCP	Internet	Dokploy proxy	Allow for redirect and certificate issuance
443/TCP	Approved users or internet per hospital policy	Dokploy proxy	Allow with TLS
8443/TCP	Administrator through VPN/SSH tunnel	OIE	Do not expose publicly
Device ports	Laboratory or radiology VLAN	OIE/Orthanc	Allow only the exact approved sources and protocols
5432/TCP	Internal containers	PostgreSQL services	Never publish publicly

Values to prepare

Long random database and keystore passwords

A Laravel APP_KEY generated once for each environment

Mail server credentials and an approved sender address

Backup repository URL, access key, secret key, and encryption password

Domain names and DNS access

Integration tokens with minimum Sanctum abilities

OIE channel exports and mapping worksheets

Proceed when DNS resolves, the server is patched, backup storage is available, ownership is assigned, and no production secret has been placed in the repository.

Getting started

Local development

Dokploy deployment

Initial configuration

Integrations

Operations

Required DNS names

Network access

Values to prepare

​Required DNS names

​Network access

​Values to prepare

Required DNS names

Network access

Values to prepare