# Infrastructure configuration for development environment (Docker)
# Auto-generated by `mecha10 init`
#
# This config assumes services running in Docker network

# Local Redis (on-robot message bus)
redis:
  url: redis://mecha10-redis:6379
  max_connections: 10
  connection_timeout_ms: 5000

# Control plane Redis (robot-to-cloud communication)
# Optional - only used when connecting to Mecha10 cloud services
# Uncomment to enable dual Redis architecture for K8s-like deployment
# control_plane_redis:
#   url: redis://mecha10-control-plane-redis:6379
#   max_connections: 5
#   connection_timeout_ms: 10000

# Redis bridge (message forwarding between local and control plane)
# Only active when control_plane_redis is configured
# bridge:
#   enabled: true
#   robot_id: my-robot  # Optional: prefix topics with robot ID
#   local_topics:
#     - "/sensor/camera/*"   # Keep high-frequency sensor data local
#     - "/sensor/lidar/*"
#     - "/sensor/imu/*"
#   bridged_topics:
#     - "/system/*"          # Forward system topics to control plane
#     - "/telemetry/*"       # Forward telemetry
#     - "/logs/*"            # Forward logs
#     - "/fleet/*"           # Forward fleet management

# PostgreSQL (API/platform database)
postgres:
  host: mecha10-postgres
  port: 5432
  database: mecha10
  username: mecha10
  password: mecha10_dev
  max_connections: 5

# MLflow (experiment tracking)
mlflow:
  tracking_uri: http://mecha10-mlflow:5000
  artifact_location: s3://mlflow/artifacts

# MinIO (object storage)
minio:
  endpoint: http://mecha10-minio:9000
  access_key: mecha10
  secret_key: mecha10_dev
  secure: false

# Logging
logging:
  level: info
  format: json
