Skip to content

Commit 1ec7621

Browse files
waleedlatif1claude
andcommitted
fix: address the eighth review round
`docker-compose.ollama.yml` builds the app, realtime server, and migrator from source, which I had missed: - The Ollama upgrade block ran `pull` then `up -d`. That refreshes only the Ollama and Postgres images and leaves every Sim service on its old build. It is a checkout plus `build --pull` now. - The source rollback showed only the local file and no profile; the Ollama stack needs both. - Dropped the Ollama mention from the `COMPOSE_FILE` comment above, since that stack is covered by its own profile-aware commands rather than the CLI. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015BwsJTEQRzWJaY4BRCkPZt
1 parent 951f023 commit 1ec7621

1 file changed

Lines changed: 14 additions & 5 deletions

File tree

apps/docs/content/docs/platform/self-hosting/upgrades.mdx

Lines changed: 14 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -179,9 +179,10 @@ kubectl logs -n simstudio deploy/sim-app -c migrations --tail=100
179179

180180
```bash
181181
npx sim-setup update
182-
# The file that started your install — docker-compose.local.yml for a
183-
# source-built stack, docker-compose.ollama.yml for the Ollama one.
182+
# The file that started your install. The Ollama stack is not managed by
183+
# the CLI at all — see below.
184184
COMPOSE_FILE=docker-compose.prod.yml
185+
# COMPOSE_FILE=docker-compose.local.yml
185186
docker compose -f "$COMPOSE_FILE" logs migrations
186187
```
187188

@@ -199,10 +200,13 @@ Inspect the result with `npx sim-setup logs`, which targets whichever Compose fi
199200
The CLI detects only those two files. An install started from `docker-compose.ollama.yml` is invisible to it — `update`, `logs`, and `status` all report no install — so upgrade that stack directly:
200201

201202
```bash
202-
# The Ollama service is profile-scoped, so an unprofiled command silently
203-
# skips it. Use the profile you installed with.
203+
# That file builds the app, realtime server, and migrator from source, so the
204+
# upgrade is a checkout plus a rebuild — pulling only refreshes Ollama and
205+
# Postgres. The Ollama service is profile-scoped, so pass the profile you
206+
# installed with or Compose silently skips it.
204207
PROFILE=gpu # or cpu
205-
docker compose -f docker-compose.ollama.yml --profile "$PROFILE" pull
208+
git pull
209+
docker compose -f docker-compose.ollama.yml --profile "$PROFILE" build --pull
206210
docker compose -f docker-compose.ollama.yml --profile "$PROFILE" up -d
207211
```
208212

@@ -275,7 +279,12 @@ The local and Ollama stacks build the app from source and ignore `SIM_VERSION`,
275279

276280
```bash
277281
git checkout <previous-release-tag>
282+
283+
# Local stack
278284
docker compose -f docker-compose.local.yml up -d --build
285+
286+
# Ollama stack — same profile you installed with
287+
docker compose -f docker-compose.ollama.yml --profile gpu up -d --build
279288
```
280289

281290
**Rollback after a schema change** requires restoring the database to the pre-upgrade backup, because migrations are forward-only:

0 commit comments

Comments
 (0)