Installation Guide

This guide describes the installation of the Rulemapping Automation Platform (RAP) on a Linux host using Docker Compose.

Kubernetes is also an option

Rulemapping Solutions operates the platform on Kubernetes itself, and the same application can be deployed into your own cluster. That path is not covered by this guide — if you would prefer it, get in touch with us and we will work out the deployment with you.

What gets installed

Two containers, managed as one Compose project:

Container	Role
ktdocker0	The RAP application. Serves the web interface on port 8080.
rmsaimiddleware0	The AI middleware — an OpenAI-compatible gateway that holds your LLM provider credentials.

A PostgreSQL database is required but is not part of this setup. It can run on the same host or anywhere else the containers can reach.

TLS termination and public exposure are done by a reverse proxy in front of the application, which is also not part of this setup.

Steps

1. Preparation — hardware, dependencies, license
2. Container Registry — authenticating and pulling the images
3. Configuration — installation directory, application configuration
4. Compose Setup — the Compose project
5. Database — roles, schema, grants
6. Finalization — starting up and creating the first user
7. AI Middleware — LLM provider configuration
8. Case UI — optional case front-end
9. Maintenance — logs, backup, upgrades, reverse proxy

What you receive from Rulemapping Solutions

Item	Example	Used for
Prefix	acme	URL path, database and role names
License file	3240-abcd-1234-acme.cl	activates the application
Registry robot account	robot$rms+acme	pulling the container images
Registry robot password	individual per installation	pulling the container images

The license is bound to a specific application version: a ktdocker image tagged 3.24.x requires a license with :VERSION 3240.

Working without Compose

Every step in this guide can also be performed with individual docker commands. Those are collected in Appendix: Single Docker Commands — useful for troubleshooting, not as a second installation path.