ThothII/docs/installazione-docker-4-contesti.md

Installazione Docker nei contesti operativi correnti

ThothII usa una topologia Compose unica:

• frontend
• core
• qdrant
• embedding
• embedding-model-init

Qdrant e Ollama embedding sono servizi interni obbligatori del progetto Compose. Restano esterni solo DWH e LLM.

Comando standard locale

cp deploy/env/local.env.example deploy/env/local.env
cp deploy/secrets/thothii.secrets.example deploy/secrets/thothii.secrets
chmod 600 deploy/secrets/thothii.secrets

docker compose --env-file deploy/env/local.env \
  -f compose.yaml -f deploy/compose.local.yaml up --build -d

Compilare deploy/env/local.env con:

• PI_AUTH_FILE
• THT_SECRETS_FILE
• THT_WORKSPACE_GIT_REMOTE
• endpoint DWH
• endpoint LLM

Non inserire secret nel file .env. I secret runtime stanno nel bundle deploy/secrets/thothii.secrets.

Bundle dei secret

Le chiavi documentate e supportate nel bundle sono:

THT_MODEL_API_KEY=...
THT_DWH_API_KEY=...

Una CA privata PEM resta esterna al bundle e va montata con un override Compose revisionato.

Preprocessing

I job di preprocessing usano gli stessi servizi interni Qdrant/Ollama:

docker compose --env-file deploy/env/local.env \
  -f compose.yaml -f deploy/compose.local.yaml \
  -f deploy/compose.preprocess.yaml --profile preprocess run --rm preprocess-evidence

Per introspezione DWH:

docker compose --env-file deploy/env/local.env \
  -f compose.yaml -f deploy/compose.local.yaml \
  -f deploy/compose.preprocess.yaml --profile preprocess run --rm preprocess-dwh

Server

Per installazioni server usare il profilo server con overlay sessioni:

docker compose --env-file deploy/env/server.env \
  -f compose.yaml -f deploy/compose.server.yaml \
  -f deploy/compose.session-server.yaml.example up --build -d

Consultare anche:

• docs/install/local-workspace-registry.md
• docs/install/server-workspace-registry.md