B9b4ymin Jellycore Jellycore Ops

JellyCore Operations

tomevault-io Updated

File contents

JellyCore Operations

Use this runbook for production-safe service operations.

Safety Rules

  • Verify target environment before running commands.
  • Prefer read-only diagnostics before restart actions.
  • Do not run destructive Docker prune/remove commands unless explicitly requested.

Standard Flow

  1. Check status
docker compose ps
  1. Check health endpoints
curl -fsS http://localhost:47778/api/health
curl -fsS http://localhost:47779/health
  1. Inspect focused logs
docker compose logs --tail=200 oracle
docker compose logs --tail=200 nanoclaw
docker compose logs --tail=200 chromadb
  1. Recover by smallest action
docker compose restart <service>
  1. Re-verify status and health

Delivery Format

  • Incident summary (symptom, scope, likely root cause)
  • Actions taken (ordered)
  • Current status (healthy/degraded/down)
  • Next recommendation

Load references/commands.md for detailed command variants.


Source: b9b4ymiN/JellyCore — distributed by TomeVault.

tomevault-io/skills-registry/tree/main/b9b4ymin--jellycore--jellycore-ops commit ce15c2254f

Frequently asked questions

npx skillmds@latest add tomevault-io/b9b4ymin-jellycore-jellycore-ops