Documentation Center

1. Orchestration Overview

The calculation engine is packaged as an OCI-compliant container image hosted on our secure client registry. It can be orchestrated using Docker Compose, Docker Swarm, or Kubernetes pods.

2. Docker Compose Blueprint

Below is a standard boilerplate config to run the calculation engine alongside a postgres credential secrets mapping:

version: '3.8'

services:
  packcpq-engine:
    image: registry.packcpq.com/core/engine:v1.2.0
    container_name: packcpq-core
    ports:
      - "8080:8080"
      - "9090:9090"
    environment:
      - LICENSE_KEY=pk_live_YOUR_LICENSE_KEY_TOKEN
      - DB_HOST=db.local
      - DB_PORT=5432
      - DB_NAME=packcpq_pricing
      - DB_USER=postgres
      - DB_PASSWORD=/run/secrets/db_password
      - ENCRYPTION_SECRET=your_local_crypto_salt
    secrets:
      - db_password
    volumes:
      - engine-cache:/var/cache/packcpq
    restart: unless-stopped

secrets:
  db_password:
    file: ./db_password.txt

volumes:
  engine-cache:
    driver: local

3. Crucial Environment Keys

Configure the container behavior using the following environment parameters:

• LICENSE_KEY: Your commercial license token. The container checks in with https://auth.packcpq.com once every 24 hours to validate active subscription capacity.
• ENCRYPTION_SECRET: Cryptographic salt used to encrypt raw material price tables in the mounted database. Should be kept secret.
• engine-cache volume: Persists structural calculation configurations to prevent recalculation lags on reboot.