DevOps

Requirements documentation spells out supported platforms, sizing, and prerequisites so you can validate a topology before you deploy. Self-hosting via Docker explains running dotCMS in containers; the Docker environment configuration pages cover image options, environment variables, JVM, database, and search settings you will see in real environments.

Managing Evergreen on-premise documents the dotEvergreen self-hosted path when you want continuous delivery of platform updates on your own infrastructure. Cluster setup walks through auto- and manual-cluster modes for multi-node deployments.

Configuration properties documentation explains how to customize system behavior from the central properties file. Locales and language configuration pages describe multilingual setups and fallbacks.

Apps integrations covers third-party app bindings (where SAML secrets, CDNs, and similar live). dotAI’s overview states that it exposes OpenAI-powered operations across sites and apps — with linked pages for workflow actions, REST resources, admin tooling, and the MCP server for advanced AI integration.

SAML documentation covers enterprise SSO integration; assigning permissions and roles-and-tools pages explain how access maps to CMS features. User management discusses front-end versus back-end accounts.

Known security issues lists advisories; responsible disclosure states how to report defects; security best practices summarizes platform-hardening expectations. Together they give operators a checklist for audits and customer security reviews.

Performance tuning is the umbrella for JVM, database, cache, logging, and profiling levers — memory settings, cache regions and providers (including chaining and Redis), and how to observe the system under load. Docker performance considerations call out container-specific sizing, storage, and runtime choices that affect throughput and latency.

Cache configuration explains how regions and providers are wired; cache tuning goes deeper on eviction, TTLs, and getting the most from your cache stack. Load balancing documentation covers distributing traffic across nodes so clusters stay responsive as you scale out.

Multi-site management explains how to run many hostnames and sites from one dotCMS instance — adding and copying sites, dashboards, host metadata, and day-to-day operations across your fleet.

Site permissions document how access is scoped per site so teams and tenants stay isolated when they share infrastructure. Site variables cover per-site configuration values you can reference from templates and code without hard-coding environment-specific details.

System maintenance covers operational hygiene — cache flushing, index management and reindexing, log review, and utilities such as search-and-replace or trimming old asset versions. System info surfaces runtime and environment details; threads documentation helps you inspect what the JVM is doing when you need to correlate load with behavior.

Changelogs summarize what changed release by release. Current releases list the shipping artifacts you should run in production. Upgrading ties those notes to step-by-step migration work so you can plan maintenance windows with clear before-and-after expectations.