CompDesk first-run setup

1. Welcome and system check

This checker does not install privileged packages.

Checking this server…

2. Deployment mode

Recommended Docker Compose deployment Existing PostgreSQL with standalone Node.js Existing PostgreSQL with the app in Docker

PostgreSQL is the only supported database. Database data and both storage directories must use persistent volumes.

3. PostgreSQL

Provider Host Port Database Username Password TLS mode Optional CA certificate

4. Identity and network

Public application URL Application name Support email Primary color Accent color Trust a configured reverse proxy (review forwarded-header documentation)

5. First Super Admin and authentication

Local password only Local password and single sign-on Single sign-on only

Single sign-on only would lock out the first Super Admin, whose single sign-on identity is not linked yet. Choose "Local password and single sign-on"; after signing in, link your account from Profile, then disable local login in Settings → Security.

Administrator name Administrator email Local password Confirm password

Identity provider Entra tenant IDEntra client ID Entra client secret Issuer URL (exactly as in /.well-known/openid-configuration; HTTPS) Client ID Client secret

Advanced: certificates and client authentication

Identity provider CA certificate (optional, PEM; for a private CA) Token endpoint authentication Client private key (PEM, unencrypted; RSA 2048+, EC P-256 or P-384) Client certificate (optional, PEM; adds x5t#S256) Key ID (kid, optional)

Redirect URI to register with the provider:

6. Secrets and encryption

CompDesk generates independent cryptographic secrets during installation. They are written atomically to one ignored environment file with restrictive permissions and are never shown by this wizard.

7. SMTP and notifications

Configure SMTP now (optional)

HostPort UsernamePassword From addressTest recipient Implicit TLS (port 465) Require STARTTLS

8. Storage and scanning

Private attachment directory Maximum file size (MB) Files per ticket Storage per ticket (MB) Global attachment storage (GB) Temporary upload lifetime (hours) Temporary files per user Temporary storage per user (MB) Connect to a ClamAV daemon (scan errors fail closed)ClamAV hostClamAV port

Ticket attachments remain outside public static storage. Configure persistent volumes and backups for private attachments and branding assets.

9. Demo data

Install optional demo data

Explore 3 departments, 18 categories, 5 example tickets, 6 demo accounts, templates, and bilingual help articles. Disabled by default. Random demo credentials are shown once; local sign-in must be enabled to use them. Your Super Admin and settings are preserved. Remove seeded content later in Settings → Demo data.

10. Review and install

I confirm these non-secret settings and authorize migrations and installation.

Authorize setup

1. Welcome and system check

2. Deployment mode

3. PostgreSQL

4. Identity and network

5. First Super Admin and authentication

6. Secrets and encryption

7. SMTP and notifications

8. Storage and scanning

9. Demo data

10. Review and install