claude
5596cdddbc
llm.Client carries a bearer credential and sets it on the completion, and Pair signs the /health probe with it too. An unsigned probe would answer 401, Pair would read that as a card that is busy, and every workstation turn would fall back to the resident model with nothing naming why. The token comes from workstation.token, expanded from MAVEN_GPU_TOKEN like every other secret in that file. Missing, and voicewire says so at startup: the fallback is silent by design and this failure would otherwise be invisible. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ESv8hqNPseYt1CnotZpqDz
22 lines
1.0 KiB
Bash
22 lines
1.0 KiB
Bash
# Secrets for mavend's away-channel reaches. The file is still called
|
|
# telegram.env because compose names it that; it holds both reaches now.
|
|
# Copy this file to deploy/telegram.env and fill in real values.
|
|
# deploy/telegram.env is gitignored — never commit the real secrets.
|
|
TELEGRAM_BOT_TOKEN=
|
|
TELEGRAM_CHAT_ID=
|
|
|
|
# ntfy access token for the `maven` topic, the second reach (V-649). Mint it on
|
|
# the ntfy server with write access to that topic and nothing else:
|
|
# ntfy token add --expires=never maven
|
|
# Read access is not needed — mavend publishes and never subscribes.
|
|
NTFY_TOKEN=
|
|
|
|
# Bearer token for mavgpud, the workstation's GPU supervisor (V-673). It fronts
|
|
# the big model on a LAN port, so the token is the whole boundary in front of
|
|
# the card. Any long random string; mint one with:
|
|
# openssl rand -hex 32
|
|
# The same value goes in a file on workpc, named by token_file in
|
|
# deploy/mavgpud.json. Unset here and every workstation turn falls back to the
|
|
# resident model, because mavgpud answers 401 and Maven reads that as down.
|
|
MAVEN_GPU_TOKEN=
|