Skip to main content

direct_child_process_config

Function direct_child_process_config 

Source
pub fn direct_child_process_config(
    service: &str,
    iroh_required: bool,
    explicit_config: Option<&Path>,
    exe: &Path,
) -> Result<ProcessConfig>
Expand description

Build one child invocation for the direct launch path (#1585).

Required-native children run hyprstream [--config PATH] service start NAME --foreground — no --ipc, no local endpoint fallback; their readiness is the child’s own notification boundary, never a UDS socket. Compatibility children keep the historical --ipc shape. The explicit config path (when the operator supplied one) is forwarded so the child loads, validates, and pins the same configuration the launcher did; it is canonical absolute, so it stays meaningful regardless of the child’s working directory, and it is one argv element, so spaces need no quoting. Config contents, keys, and JWTs never enter argv or the environment.