fix(compose): align agentlens to current image — JWT_SECRET + health port#13
Merged
Conversation
…port The stack's agentlens was perpetually unhealthy (it was pinned to 0.12.2-era env). Two concrete causes, both fixed: 1. Current AgentLens REQUIRES JWT_SECRET — fatal at boot if unset, even with AUTH_DISABLED=true. The compose only gave JWT_SECRET to agentgate. Added it to agentlens (reuses the stack's shared dev secret). 2. The image's built-in HEALTHCHECK probes port 3400 (its default PORT), but we run it on 3000 — so the healthcheck never passed. Added a compose healthcheck that probes the real port (node fetch localhost:3000/api/stats; the node base image has no curl/wget). Verified locally: `docker compose --profile governance up -d --wait` now brings agentlens + agentgate + lore + lore-db all to (healthy). CI: re-widened the smoke test from lore-only back to the full governance profile (agentlens + agentgate + lore) with health polling on /api/stats, /health, /health. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019tXZpN29akdmG8AEjgSZwk
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The stack's
agentlenswas perpetually unhealthy (compose env was pinned to the 0.12.2 era). Two concrete causes, both fixed:JWT_SECRET— fatal at boot if unset, even withAUTH_DISABLED=true. The compose only gaveJWT_SECRETto agentgate → agentlens crashed. Added it to agentlens (reuses the stack's shared dev secret).HEALTHCHECKprobes port 3400 (its defaultPORT), but we run it on 3000, so it never passed. Added a compose healthcheck probing the real port (node fetch localhost:3000/api/stats— the node base image has no curl/wget).Verified locally:
docker compose --profile governance up -d --waitbrings agentlens + agentgate + lore + lore-db all to (healthy).CI: re-widened the smoke test from lore-only back to the full governance profile with health polling on
/api/stats,/health,/health.(The earlier diagnosis that agentlens was a "newer major incompatible with the env" was only half-right — it's these two specific env/healthcheck deltas, not a broad rewrite.)