Documentation forWeb Help Desk
Thinking of upgrading to the cloud? Learn more about migrating from Web Help Desk to Service Desk.

Optional post-installation tasks

The information on this page applies only to WHD 2026.2.1. For guidance related to other versions, see Web Help Desk Previous Version Documentation.

Use these optional tasks to customize WHD after a successful base installation.

Optional task 1: Use an external PostgreSQL database

  1. Set WHD_DB_HOST, WHD_DB_PORT, WHD_DB_NAME, WHD_DB_USER, and WHD_DB_PASSWORD in conf/whd.env.

  2. Restart backend service and validate datasource connectivity.

Optional task 2: Replace default TLS certificate

  1. Replace conf/cert.pem and conf/key.pem with CA-signed files.

  2. Restart Caddy service and verify certificate chain from a browser or openssl.

Optional task 3: Customize HTTP behavior

  1. Use WHD_HTTP_IMPORT=http-redirect.caddy (default) to force HTTPS.

  2. Use WHD_HTTP_IMPORT=http-serve.caddy only for legacy/non-redirect behavior when approved.

Optional task 4: Tune JVM memory

  1. Adjust WHD_JVM_MIN_MEMORY and WHD_JVM_MAX_MEMORY in conf/whd.env for larger deployments.

  2. Restart backend service after memory changes.

Optional task 5: FIPS mode (Windows only)

  1. Set WHD_FIPS_ENABLED=true in conf/whd.env after completing required Windows FIPS prerequisites.

  2. Use the FIPS setup guide to validate provider registration and TLS behavior.

Important note on bundled runtimes

Current WHD installs include bundled JDK and Node.js runtimes. Legacy whd.conf-based runtime replacement procedures are not applicable to current versions. If runtime customization is required, keep the same supported major versions and validate fully in non-production first.