zeroclaw/docs/ops
simianastronaut 41b46f23e3 docs(setup): add Docker/Podman stop/restart instructions
Users who installed via `./install.sh --docker` had no documented way to
restart the container after stopping it. Add clear lifecycle instructions
(stop, start, restart, logs, health check) to both the bootstrap guide and
the operations runbook, covering docker-compose, manual `docker run`, and
Podman-specific flags.

Closes #3474

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-15 16:26:28 -04:00
..
network-deployment.md docs: update all internal links to match topic-based directory layout 2026-03-09 23:09:09 -04:00
operations-runbook.md docs(setup): add Docker/Podman stop/restart instructions 2026-03-15 16:26:28 -04:00
proxy-agent-playbook.md docs: restructure docs/ into topic-based directory layout 2026-03-09 22:25:20 -04:00
README.md docs: update all internal links to match topic-based directory layout 2026-03-09 23:09:09 -04:00
resource-limits.md docs: update all internal links to match topic-based directory layout 2026-03-09 23:09:09 -04:00
troubleshooting.md docs: replace main branch references with master (#3194) 2026-03-11 21:54:08 -04:00
troubleshooting.vi.md docs: update all internal links to match topic-based directory layout 2026-03-09 23:09:09 -04:00

Operations & Deployment Docs

For operators running ZeroClaw in persistent or production-like environments.

Core Operations

Common Flow

  1. Validate runtime (status, doctor, channel doctor)
  2. Apply one config change at a time
  3. Restart service/daemon
  4. Verify channel and gateway health
  5. Roll back quickly if behavior regresses