Support remote Ollama servers (or none) at install time

↗ view on GitHub · Claude · 2026-05-15 · b3ad3540

The bundled ollama service in docker-compose.yml moves behind a
new `local-ollama` profile, so docker compose only starts the
container when COMPOSE_PROFILES includes that profile.

install.sh now asks how PIP should reach Ollama:
  local   bundled in this compose stack (previous default)
  remote  point at an existing Ollama server URL
  none    no local AI, external providers only

The choice writes OLLAMA_MODE, LOCAL_LLM_BASE_URL, and
COMPOSE_PROFILES into .env.compose. The compose wrapper in
install.sh and update.sh sources the env file so subsequent
docker compose invocations honour the profile. The model-pull
wizard step and image pull are skipped when not in local mode.

The bundled image is also no longer in the unconditional pull
batch; remote/none deployments shouldn't have to download a
~1 GB image they'll never run.

Also fixes .gitignore so .env.compose.example is tracked (the
file is referenced by docker-compose.yml's header comment but
was being silently ignored by the broad .env.* rule).
Repository cpatpa/PIP
Author Claude <noreply@anthropic.com>
Authored
Parents aa20b742
Stats 6 files changed , +175 , -18
Part of Bare-metal installer + operator tooling

Capture this commit into my fork

Download a Markdown prompt that tells Claude how to port this exact commit into your working tree. Run it via claude -p < capture-commit-b3ad3540.md from inside the repo you want the change in.

⬇ Download capture-commit-b3ad3540.md