# Phase 1 lab_hosts seed — applied to the DB at Provisioner startup (config.js
# applyLabHostsSeed), not managed via a runtime API (no host-management endpoints in Phase 1,
# matching "don't overbuild scheduling yet" — see docs/PHASE1_PLATFORM_FOUNDATION.md §4).
#
# Exactly one enabled row for Phase 1. Swapping this for a remote tcp://<lab-host-vm>:2376
# entry with TLS material is the entire code change needed to point at a real, separate Lab
# Host VM in production — see docs/LAB_ARCHITECTURE.md §1 and correction D.

lab_hosts:
  - lab_host_id: dev-local
    display_name: "Local development Docker socket"
    endpoint: "unix:///var/run/docker.sock"
    enabled: true

  # Production example (not active — shown for reference; uncomment and fill in when a real
  # Lab Host VM exists):
  # - lab_host_id: labhost-01
  #   display_name: "RootNode Lab Host VM 01"
  #   endpoint: "tcp://10.20.30.5:2376"
  #   tls_ca_path: /etc/rootnode/tls/labhost-01/ca.pem
  #   tls_cert_path: /etc/rootnode/tls/labhost-01/cert.pem
  #   tls_key_path: /etc/rootnode/tls/labhost-01/key.pem
  #   enabled: true