The user asked to drop it: nobody had the Gemini CLI login or a key set up, and Exa then Wikipedia cover the voice use. webSearch is now live Chrome, Exa, Brave (opt-in), Wikipedia. Removes the CLI/REST backends, the GEMINI_* settings, the Docker login mount and checks, and updates the specs and docs/llm_contexts.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
145 lines
5.6 KiB
Markdown
145 lines
5.6 KiB
Markdown
# Deployment layouts
|
||
|
||
One image, three roles (`JARVIS_ROLE`), selected in `.env`. GPU is added per OS
|
||
via a compose override picked with `COMPOSE_FILE`.
|
||
|
||
> `COMPOSE_FILE`'s file separator is OS-specific: Linux/macOS use `:`, Windows
|
||
> uses `;` (a colon collides with the `C:` drive letter). Using `:` on Windows
|
||
> yields `... The system cannot find the file specified`. If in doubt, leave
|
||
> `COMPOSE_FILE` unset and pass the files explicitly:
|
||
> `docker compose -f docker-compose.yml -f docker-compose.gpu-windows.yml up -d`.
|
||
|
||
## A. All-in-one (single machine)
|
||
|
||
Everything (desktop + Chrome + bridge + bot + TTS) in one container.
|
||
|
||
```
|
||
# .env
|
||
JARVIS_ROLE=full
|
||
COMPOSE_FILE=docker-compose.yml:docker-compose.gpu-linux.yml # Ubuntu/macOS (":" )
|
||
# COMPOSE_FILE=docker-compose.yml;docker-compose.gpu-windows.yml # Windows 11 (";" )
|
||
DISCORD_SELFBOT_TOKEN=...
|
||
DISCORD_GUILD_ID=...
|
||
|
||
docker compose up -d # Ollama + javis (COMPOSE_FILE adds GPU)
|
||
```
|
||
|
||
## B. Split: browser host (LAN) + bot on your PC
|
||
|
||
The on-screen Chrome, real mouse/keyboard (xdotool) and screen live on the
|
||
**browser host**. Your PC runs the **bot** and drives that browser over the
|
||
internal network — no auth (internal only).
|
||
|
||
### Browser host (the LAN machine that shows Chrome, e.g. 192.168.10.5)
|
||
|
||
```
|
||
# .env
|
||
JARVIS_ROLE=browser
|
||
CDP_BIND=0.0.0.0
|
||
BROWSER_CONTROL_BIND=0.0.0.0
|
||
CDP_PUBLISH_BIND=0.0.0.0
|
||
# no GPU needed → leave COMPOSE_FILE unset (base compose only)
|
||
|
||
docker compose up -d javis # desktop + Chrome + control-server (port 8777)
|
||
```
|
||
|
||
Watch it on this machine’s VNC (`localhost:5901`) / noVNC (`localhost:6080`).
|
||
|
||
### Bot host (your PC — Ubuntu or Windows 11)
|
||
|
||
```
|
||
# .env
|
||
JARVIS_ROLE=bot
|
||
BROWSER_CONTROL_URL=http://192.168.10.5:8777 # the browser host's LAN IP
|
||
COMPOSE_FILE=docker-compose.yml:docker-compose.gpu-linux.yml # Ubuntu/macOS (":" )
|
||
# COMPOSE_FILE=docker-compose.yml;docker-compose.gpu-windows.yml # Windows 11 (";" )
|
||
DISCORD_SELFBOT_TOKEN=...
|
||
DISCORD_GUILD_ID=...
|
||
|
||
docker compose up -d # bot + bridge + TTS + Ollama (GPU per OS)
|
||
```
|
||
|
||
The bot’s `controlBrowser` tool posts commands to `BROWSER_CONTROL_URL`, so
|
||
"네이버에서 X 검색", "구글로 돌아가" etc. drive the **browser host’s** Chrome with real
|
||
human-style input (visible on its VNC).
|
||
|
||
### External Ollama (LLM on a separate host)
|
||
|
||
To run Ollama on a different LAN machine (e.g. a dedicated GPU host at
|
||
`192.168.10.9`) instead of inside this stack:
|
||
|
||
```
|
||
# .env on the app host
|
||
OLLAMA_BASE_URL=http://192.168.10.9:11434
|
||
```
|
||
|
||
Then start the app WITHOUT the in-stack LLM services: `docker compose up -d javis`
|
||
(do not `docker compose up -d`, which would also start `ollama`/`ollama-init`).
|
||
On the LLM host, make Ollama listen on the LAN (`OLLAMA_HOST=0.0.0.0:11434`) and
|
||
pull the models there (`ollama pull <chat>`, `<intent>`, `<embed>`). The compose
|
||
respects `OLLAMA_BASE_URL`, defaulting to the in-stack `ollama` service when unset.
|
||
|
||
## C. GPU split: brain host (.9, GPU) + app host (.5, no GPU)
|
||
|
||
All the GPU-heavy compute (Whisper STT, the Ollama LLM, and TTS) runs on the
|
||
**brain host** (a GPU box, e.g. `192.168.10.9`). The **app host** (no GPU, e.g.
|
||
`192.168.10.5`) runs the Discord bot and the on-screen browser, and offloads
|
||
every STT/LLM/TTS call to the brain over the LAN.
|
||
|
||
Flow: the bot (app host) POSTs captured voice to the brain's bridge; the brain
|
||
runs STT -> LLM -> TTS on the GPU and returns the reply audio; when the LLM
|
||
drives the browser, the brain's `controlBrowser` tool POSTs to the app host's
|
||
control-server (port 8777), so Chrome moves on the app host's screen.
|
||
|
||
### Brain host (.9 — GPU: STT + LLM + TTS)
|
||
|
||
```
|
||
# .env
|
||
JARVIS_ROLE=brain
|
||
BRIDGE_HOST=0.0.0.0 # bridge listens on the LAN
|
||
SETTINGS_PUBLISH_BIND=0.0.0.0 # publish bridge port 8765 to the LAN
|
||
OLLAMA_BASE_URL=http://192.168.10.9:11434 # Ollama on this host (bind 0.0.0.0)
|
||
OLLAMA_CHAT_MODEL=qwen2.5:7b
|
||
WHISPER_DEVICE=cuda # STT on the GPU
|
||
WHISPER_COMPUTE_TYPE=float16
|
||
TTS_ENGINE=melo # GPU MeloTTS (offline, privacy-first)
|
||
MELO_DEVICE=cuda # TTS on the GPU (melo-worker)
|
||
BROWSER_CONTROL_URL=http://192.168.10.5:8777 # drive the app host's Chrome
|
||
COMPOSE_FILE=docker-compose.yml:docker-compose.gpu-linux.yml # GPU (":" on Linux)
|
||
|
||
# STT (Whisper), LLM (Ollama) and TTS (MeloTTS) all run on this host's GPU.
|
||
# Ollama listens on 0.0.0.0:11434 (systemd or a container).
|
||
docker compose up -d javis # brain bridge + melo-worker only (no bot, no desktop)
|
||
```
|
||
|
||
### App host (.5 — bot + browser, no GPU)
|
||
|
||
```
|
||
# .env
|
||
JARVIS_ROLE=app
|
||
BRIDGE_URL=http://192.168.10.9:8765 # offload STT/LLM/TTS to the brain
|
||
CDP_PUBLISH_BIND=0.0.0.0 # publish control-server 8777 to the LAN
|
||
STREAM_HW=0 # no NVENC on a no-GPU host
|
||
DISCORD_SELFBOT_TOKEN=...
|
||
DISCORD_GUILD_ID=...
|
||
# no GPU → leave COMPOSE_FILE unset (base compose only)
|
||
|
||
docker compose up -d javis # bot + desktop + Chrome + control-server
|
||
```
|
||
|
||
The `brain` and `app` roles are backward-compatible additions to `full`/`browser`
|
||
/`bot`; see `docker/run-if-role.sh`.
|
||
|
||
## Windows 11 notes
|
||
|
||
- Install the NVIDIA driver on Windows and enable GPU in Docker Desktop
|
||
(Settings → Resources → WSL Integration). Use the `gpu-windows.yml` override.
|
||
- Paths: named volumes are cross-platform.
|
||
|
||
## Known limitation
|
||
|
||
Discord Go-Live broadcast of the **browser host's** screen from a **remote** bot
|
||
is not supported (the bot's WebRTC screen capture is local to the bot machine).
|
||
Use the browser host's VNC to view it. A full remote-broadcast path is separate,
|
||
larger work.
|