Prerequisites:
-
The Device Registration Portal installation package extracted on the host
-
The Address Manager and DNS/DHCP Server environments configured as described in the Address Manager configuration section
-
All required values collected (hostname, BAM IP, LDAP/AD details, etc.)
-
Configure the environment
-
Copy the environment template and edit
.env:cp .env.prod .env -
It is recommended to fill in all required values. Set the following values as a minimum:
Value Description PUBLIC_BASE_HOSTThe public hostname users will access. PUBLIC_BASE_IPThe public IP users can access. FRONTEND_HOST<http://<PUBLIC_BASE_HOST>>BACKEND_CORS_ORIGINS["http://drp","https://<PUBLIC_BASE_HOST>","http://<PUBLIC_BASE_IP>","https://<PUBLIC_BASE_IP>"]POSTGRES_PASSWORDA strong database password. DATABASE_URLUpdate with the chosen password. DRP_BAM_URL,DRP_BAM_USERNAME,DRP_BAM_PASSWORDBAM connection details TRUSTED_IPSYour network's CIDR (Classless Inter-Domain Routing) range. For example: 10.240.254.0/24,10.244.23.128/25TLS_DEFAULT_COMMON_NAMESet to PUBLIC_BASE_HOST.
-
-
Enable TLS certificates (required before first start)
To enforce HTTPS, it is strongly recommended to place a valid certificate under the correct path before starting the application:cp your-cert.crt certificates/traefik/tls.crt cp your-key.key certificates/traefik/tls.keyRequirements:- Files must be PEM-encoded
- The certificate SAN must include the
PUBLIC_BASE_HOSTvalue
Important: If a valid certificate is not provided, DRP will generate a temporary self-signed certificate on first start. Replace it with a valid certificate as soon as possible. -
Start the application
-
Online installation
docker login quay.io docker compose pull docker compose up -d -
Offline installation
docker load -i drp-images.tar.gz docker compose up -d
-