From 30f2a8172e5d7fc749fa7074dbc6f6534aaf3f5b Mon Sep 17 00:00:00 2001 From: Amit Paz Date: Sat, 27 Jun 2026 09:18:00 +0300 Subject: [PATCH] fix(compose): pass LORE_API_KEY to the lore service for out-of-box provisioning MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The lore service got no LORE_API_KEY, so a Postgres-backed Lore came up with no org and no API key — every call 401'd, including AgentLens→Lore, even though health was green. Pair with lore's new LORE_API_KEY root-key seeding: the lore service now receives the same shared key AgentLens uses, so the stack is usable without a manual POST /v1/org/init. (Effective once the lore image carrying the seeding ships to ghcr :latest; harmless on the current image, which ignores it.) Co-Authored-By: Claude Opus 4.8 (1M context) Claude-Session: https://claude.ai/code/session_019tXZpN29akdmG8AEjgSZwk --- docker-compose.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docker-compose.yml b/docker-compose.yml index c55bb75..9b5acf8 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -93,6 +93,10 @@ services: - "8765:8765" environment: - DATABASE_URL=postgresql://lore:lore@lore-db:5432/lore + # Seeds Lore's root API key on first boot (when the DB is empty) so the + # stack is usable without a manual POST /v1/org/init. MUST be the same + # value AgentLens uses to call Lore (shared .env var). + - LORE_API_KEY=${LORE_API_KEY:?set LORE_API_KEY in .env (copy from .env.example)} volumes: - lore-data:/app/data networks: