chore(deploy): reconcile repo docker-compose with VPS — add SIPHER_MODEL + TORQUE_*#307
Merged
Merged
Conversation
…DEL + TORQUE_*
The VPS-hosted docker-compose.yml has drifted from the repo's. This PR
brings the repo file forward (canonical) so future deploys start from a
consistent base.
Adds to repo compose:
- SIPHER_MODEL=${SIPHER_MODEL:-anthropic/claude-sonnet-4.6}
Dot-form default. The VPS compose had a HYPHEN-form default
(claude-sonnet-4-6), which silently failed getSipherModel() and
emitted empty content on every chat turn. That outage took
frontier_sip_17 to catch. The dot-form default here means even if
.env unsets SIPHER_MODEL, the agent boots with a working model.
- TORQUE_GROWTH_ENABLED=${TORQUE_GROWTH_ENABLED:-false}
- TORQUE_API_TOKEN=${TORQUE_API_TOKEN:-}
- TORQUE_INGESTER_URL=${TORQUE_INGESTER_URL:-https://ingest.torque.so}
Frontier_sip_12 added these to the VPS compose for the Torque MCP
integration but never landed them in the repo. Defaults are
fail-closed (TORQUE_GROWTH_ENABLED=false), so adding the
declarations is zero-impact for environments that don't opt in.
Does NOT add SIPHER_OPENROUTER_API_KEY — sipher#295 dropped that name
across the repo because pi-ai only reads OPENROUTER_API_KEY. The VPS
should drop its declaration next deploy.
Out of scope for this PR (followups for the deploy story, not repo
source-of-truth):
- SENTINEL_MODE default discrepancy (repo :-advisory / VPS :-yolo).
Repo's fail-safe default is correct; if VPS wants yolo, set it via
.env not compose.
- SENTINEL_AUTHORITY_KEYPAIR + JWT_EXPIRY declarations missing on
VPS — VPS should add these to match repo.
- CI check linting VPS compose vs repo HEAD on deploy — would catch
future drift automatically. Not added here; would need a workflow
edit + safe-handling for legitimate VPS-only env additions.
Closes #294.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Closes #294. The VPS-hosted
docker-compose.ymlhad drifted from the repo's. This PR brings the repo file forward (canonical) so future deploys start from a consistent base.What's added
SIPHER_MODELanthropic/claude-sonnet-4.6(dot-form)claude-sonnet-4-6) that silently failedgetSipherModel()and emitted empty content — the outage that frontier_sip_17 caught. Dot-form here means even if.envunsets the var, the agent boots with a working model.TORQUE_GROWTH_ENABLEDfalsetrue.TORQUE_API_TOKENTORQUE_GROWTH_ENABLED=true.TORQUE_INGESTER_URLhttps://ingest.torque.sofrontier_sip_12added the Torque vars to the VPS compose but never landed them in the repo. This closes that gap.What's NOT added
SIPHER_OPENROUTER_API_KEY— dropped in cleanup(env): drop dead SIPHER_OPENROUTER_API_KEY — pi-ai only reads OPENROUTER_API_KEY #295. pi-ai only readsOPENROUTER_API_KEY. The VPS should drop its declaration next deploy.Out of scope (follow-ups)
These are noted in #294's drift table but aren't repo source-of-truth fixes — they need separate deploy-side action:
SENTINEL_MODEdefault discrepancy (repo:-advisory/ VPS:-yolo). Repo's fail-safe default is correct; VPS can override via.envif it wants yolo.SENTINEL_AUTHORITY_KEYPAIR+JWT_EXPIRYdeclarations missing on VPS — VPS should add these to match repo.Test plan
docker compose configvalidates syntax + interpolates defaults correctly..env.