Deployment

Docker compose

The base docker-compose.yml brings up the full stack: CLI, ChronoVisor engine, PostgreSQL, the Web Dashboard, and the OHLCV collector.

1cp .env.example .env       # Configure API keys2docker compose up -d        # Bring everything up

Services exposed by default:

Production overlay

docker-compose.prod.yml layers production hardening on top of the base compose:

• restart: always on every service
• JSON log rotation (10 MB × 3 files per service)
• The vizzor-backup sidecar — runs scripts/backup.sh every 6 hours with 14-day retention

1docker compose -f docker-compose.yml -f docker-compose.prod.yml \2--env-file .env up -d

The bot exposes a /health endpoint compatible with UptimeRobot, BetterStack, and Docker healthchecks:

1curl http://localhost:7101/health2# → {"ok":true,"status":"healthy",...}

Backup + restore

Both scripts ship in scripts/ and are wired to the vizzor-backup sidecar:

Health monitoring

The /health endpoint returns a structured payload with per-subsystem status:

{
  "ok": true,
  "status": "healthy",
  "subsystems": {
    "engine": "healthy",
    "ml_sidecar": "healthy",
    "db": "healthy",
    "telegram": "healthy",
    "discord": "skipped"
  },
  "uptimeSeconds": 87412,
  "lastPredictionAt": "2025-12-10T14:32:11Z"
}

Wire this to your monitor of choice — the subsystems map shows which leg is degraded so on-call has actionable signal.

State persistence

The vizzor_state volume holds everything that must survive a restart:

• Per-symbol-per-family Platt calibrator shards
• FOL rule tracker (per-rule accuracy + auto CF dampening)
• Volatility registry (per-symbol ATR multipliers)
• Horizon calibration table
• Runtime allowlist
• Scheduler runtime knobs (quality-gate / vol-adapter / auto-disable per slot)
• Resolved prediction history (drives tracked WR)

Backups cover this volume, the Postgres database, and ~/.vizzor/config.yaml. Wallet files (~/.vizzor/wallets/) are not part of automated backups — they require interactive passphrase entry and live under operator control.

Updates

1# In-place update2vizzor update                      # checks GitHub releases + npm3 4# Docker stack5docker compose pull6docker compose up -d

Updates that touch the vizzor_state schema run idempotent migrations on first start; restores from older backups remain compatible.