24 lines
1.0 KiB
Markdown
24 lines
1.0 KiB
Markdown
---
|
|
id: TASK-MEDIUM.9
|
|
title: Wire ollama into rspace sidecar lifecycle
|
|
status: To Do
|
|
assignee: []
|
|
created_date: '2026-04-16 23:17'
|
|
labels: []
|
|
dependencies: []
|
|
parent_task_id: TASK-MEDIUM
|
|
---
|
|
|
|
## Description
|
|
|
|
<!-- SECTION:DESCRIPTION:BEGIN -->
|
|
server/sidecar-manager.ts lists ollama in SIDECARS but there's no ollama service in /opt/rspace-online/docker-compose.yml. ensureSidecar('ollama') calls from server/index.ts:2853 silently no-op. Either: (a) add an ollama service to the compose under profiles:[sidecar] so Sablier can wake it, or (b) drop ollama from sidecar-manager and adjust callers. Memory doc (2026-03-31 entry) suggests ollama was intended as a sidecar — option (a) is more likely correct.
|
|
<!-- SECTION:DESCRIPTION:END -->
|
|
|
|
## Acceptance Criteria
|
|
<!-- AC:BEGIN -->
|
|
- [ ] #1 ollama container exists on rspace-internal network at host 'ollama' port 11434
|
|
- [ ] #2 Sablier can wake it via blocking API
|
|
- [ ] #3 fetch('http://ollama:11434/') from rspace returns 200 after ensureSidecar('ollama')
|
|
<!-- AC:END -->
|