On-premise with Docker Compose
An overview of the Docker Compose delivery and the procedure sequence for installing MassAccess on one Linux server.
InformationThe commands on this page apply to the Docker Compose delivery.
Terms used in this guide
- A reverse proxy accepts external requests and forwards them to MassAccess services.
- Transport Layer Security (TLS) encrypts connections to the public address.
- A health check confirms that a service is ready to handle requests.
- Enrollment binds an installed instance to the created license.
Docker Compose
A self-contained 14-service stack for one customer-managed Linux server.
- Docker Compose archive with install, healthcheck, upgrade, and rollback scripts
- Bundled PostgreSQL, Kafka, ClickHouse, and Redis with six isolated volumes
- Host-level reverse proxy, TLS, monitoring, backup, and restore are operated by your team
Guide sections
Environment requirements
Minimum and recommended server parameters for deploying the on-premise version.
Environment requirementsInstallation
Obtaining the delivery package, running the installer, enrollment and verifying the health of all 14 services.
InstallationConfiguration
Configuring reverse proxy and TLS.
ConfigurationUpgrade and rollback
Upgrading the on-premise version to a new immutable version with automatic rollback on failure.
Upgrade and rollbackBackup and restore
Regular backup of data and configuration, and restore from a copy of the same installation.
Backup and restoreDiagnostics and troubleshooting
Health checks, enrollment errors, license statuses, log rotation and common issues.
Diagnostics and troubleshooting