Plan a self-hosted environment
The current self-hosted quick start describes a single Linux-server evaluation using Docker Compose. Plan separate web, API, and events hostnames. Infrastructure operation is a separate learning path from department administration.
Configure, initialize, verify
Review the supported installer, generate deployment-specific credentials, and inspect the resulting configuration. Start the stack, review worker migration progress, and verify all three endpoints. Create the first account and department after initialization.
Department settings and host settings
Department screens configure operational behavior. In this checkout, host configuration uses public static fields in configuration classes. The configuration processor reads JSON keys or environment variables and assigns those fields. Use the source and release documentation to identify the exact host setting; avoid applying a generic appsettings recipe.
Operate and recover the system
Before updating, back up the data and configuration and retain prior image references. A rollback can require restoring the database as well as the application. Treat a running evaluation as the start of operations preparation, with monitoring and a tested recovery procedure.
Choose the infrastructure walkthrough
Choose the deployment layout you will verify: Linux Compose, Windows, Kubernetes or k3s, or an Incident Command Kit. Record the supported release and verify installation, endpoint connectivity, backup, and recovery in that environment. Use the linked official guides for the matching layout.