Module project 

Project configuration types

Types for loading and managing mecha10.json project configuration files.

Structs

BehaviorsConfig

Behavior tree configuration

DatabaseServiceConfig

DockerServicesConfig

Docker services configuration for project-level Docker Compose management

EnvironmentConfig

Configuration for a specific environment

EnvironmentsConfig

Environment-specific configuration

HttpApiServiceConfig

JobProcessorServiceConfig

LifecycleConfig

Lifecycle configuration for mode-based node management

LoggingConfig

Logging configuration for a single environment (environments.<env>.logging).

ModeConfig

Configuration for a single operational mode

NodeSpec

Parsed node specification from namespaced string format

NodesConfig

Nodes configuration - map of node identifiers to versions

ProjectConfig

ProjectSimulationConfig

Project-level simulation configuration stored in mecha10.json

RobotConfig

ScheduledTaskConfig

SchedulerServiceConfig

ServicesConfig

TargetsConfig

Target execution configuration - defines where nodes run

TurnConfig

Resolved TURN server config: relay URL + credentials for a TURN entry in a WebRTC ICE server list. Kept as a standalone type here (rather than reusing mecha10_video::webrtc::connection::TurnServerConfig) since mecha10-cli-core intentionally doesn’t depend on mecha10-video - mecha10-video and the nodes that embed it (camera, video-streamer) are meant to stay lightweight for robot binaries, the same “minimal dependencies” rationale mecha10-node-resolver documents for inlining its own copy of DEFAULT_MECHA10_API_URL instead of depending on this crate.

Enums

NodeSource

Node source type based on namespace prefix

NodeTarget

Target type for node execution

Functions

load_project_config

Load full project config from mecha10.json

load_robot_id

Load robot_id from mecha10.json

turn_config

Resolve TURN server config, highest priority first: