Remove legacy hero-osis sidecar container from dev VM #62

Closed
opened 2026-04-03 17:20:31 +00:00 by mik-tf · 1 comment
Member

Problem

The dev VM still runs hero-osis container (:3377) from the pre-Phase 1 architecture. Since commit 6a73bf3 (Phase 1, issue mycelium_code/home#34), OSIS is embedded in the marketplace binary — the sidecar is unused.

Evidence

app-hero-osis-1  forge.ourworld.tf/lhumina_code/hero_osis:development  Up 42 hours (healthy)

It wastes memory and confuses the architecture.

Fix

  • Remove hero-osis service from docker-compose.yml on dev VM
  • Remove from setup.sh if referenced
  • Keep hero-ledger — that's still used for on-chain data

— mik-tf

## Problem The dev VM still runs `hero-osis` container (`:3377`) from the pre-Phase 1 architecture. Since commit `6a73bf3` (Phase 1, issue https://forge.ourworld.tf/mycelium_code/home/issues/34), OSIS is embedded in the marketplace binary — the sidecar is unused. ## Evidence ``` app-hero-osis-1 forge.ourworld.tf/lhumina_code/hero_osis:development Up 42 hours (healthy) ``` It wastes memory and confuses the architecture. ## Fix - Remove `hero-osis` service from `docker-compose.yml` on dev VM - Remove from `setup.sh` if referenced - Keep `hero-ledger` — that's still used for on-chain data — mik-tf
Author
Member

Removed hero-osis container from dev VM. Updated docker-compose.yml: removed hero-osis service + osis_data volume, added socket mount, fixed admin RPC URL with base path.

— mik-tf

Removed hero-osis container from dev VM. Updated docker-compose.yml: removed hero-osis service + osis_data volume, added socket mount, fixed admin RPC URL with base path. — mik-tf
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coopcloud_code/home#62
No description provided.