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

    The complete single-node Compose stack needs startup/steady-state measurements. CPU/RAM thresholds below are provisional warning thresholds, not verified sizing of the new model.

    Environment requirements

  • Installation

    Obtaining the delivery package, running the installer, enrollment and verifying the health of all 14 services.

    Installation

  • Configuration

    Configuring reverse proxy and TLS.

    Configuration

  • Upgrade and rollback

    Full-release upgrade with compatibility checks and guarded rollback.

    Upgrade and rollback

  • Backup and restore

    Regular backup of data and configuration, and restore from a copy of the same installation.

    Backup and restore

  • Diagnostics and troubleshooting

    Health checks, enrollment errors, license statuses, log rotation and common issues.

    Diagnostics and troubleshooting