Some checks failed
Release / semantic-release (push) Successful in 30s
tests / Unit tests (Linux, Python 3.11) (push) Failing after 5m17s
Release / build-linux (push) Failing after 7m3s
Release / build-windows (push) Has been cancelled
Release / build-macos (arm64, macos-latest) (push) Has been cancelled
Release / build-macos (x64, macos-15-intel) (push) Has been cancelled
Release / release-main (push) Has been cancelled
Release / release-develop (push) Has been cancelled
docker/jarvis-config.template.json hardcoded "tts_engine": "piper". entrypoint
renders it into /app/config/jarvis.json, and bridge _tts_engine_setting() reads
that JSON BEFORE the env — so TTS_ENGINE=melo in .env was ignored and the bot
synthesised Korean with the English Piper voice (the "foreign accent" the user
heard); the warm melo-worker sat unused.
Template now carries ${TTS_ENGINE}; compose sets TTS_ENGINE=${TTS_ENGINE:-melo}
so envsubst renders the real engine. Verified: envsubst with TTS_ENGINE=melo
yields "tts_engine": "melo", and `docker compose config` passes TTS_ENGINE=melo.
Added a regression test that the template stays env-driven and renders the
configured engine.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
20 lines
644 B
JSON
20 lines
644 B
JSON
{
|
|
"db_path": "${JARVIS_DB_PATH}",
|
|
"sqlite_vss_path": null,
|
|
"ollama_base_url": "${OLLAMA_BASE_URL}",
|
|
"ollama_embed_model": "${OLLAMA_EMBED_MODEL}",
|
|
"ollama_chat_model": "${OLLAMA_CHAT_MODEL}",
|
|
"intent_judge_model": "${OLLAMA_INTENT_MODEL}",
|
|
"tts_enabled": true,
|
|
"tts_engine": "${TTS_ENGINE}",
|
|
"tts_piper_model_path": "${TTS_PIPER_MODEL_PATH}",
|
|
"whisper_model": "${WHISPER_MODEL}",
|
|
"whisper_backend": "faster-whisper",
|
|
"whisper_device": "${WHISPER_DEVICE}",
|
|
"whisper_compute_type": "${WHISPER_COMPUTE_TYPE}",
|
|
"location_enabled": true,
|
|
"web_search_enabled": true,
|
|
"wikipedia_fallback_enabled": true,
|
|
"mcps": {}
|
|
}
|