AtlatestRenderedmarkdown

sigil-http3 / tree / docstool-configuration.md

Read the source

Readme

Tool configuration

The live browser and phone helpers are experimental examples. Supply an exact numeric bind address, certificate, origin and completed input build for the host where they run. They check ownership, hashes, certificates, host identity, port bounds and lifetimes before starting their child processes.

SettingPurpose
HTTP3_QUIC_SOURCE / HTTP3_NAT_SOURCECompanion Git source, local path or URL
HTTP3_SDK_SOURCEGit source containing the socket groundwork in spike-sdk.rev
HTTP3_SPIKE_SDK_SOURCEBuilt checkout of that SDK, including its bootstrap executable
SIGIL_BUILDERCompiler executable, default sigil
HTTP3_WORKSPACE_ROOTParent of completed input workspaces; default build/workspaces in JavaScript helpers
HTTP3_INPUT_DIRECTORY / HTTP3_INPUT_JOBCompleted trace input directory and its metadata identity
HTTP3_VERIFIED_NATIVE_JOBCompleted echo workspace name under HTTP3_WORKSPACE_ROOT
HTTP3_IPV4_ADDRESSExact IPv4 bind address, default 127.0.0.1
HTTP3_IPV6_ADDRESSExplicit global IPv6 bind for live direct tests
HTTP3_INTERFACEInterface carrying that address; no fixed interface is assumed
HTTP3_PAGE_URL / HTTP3_PAGE_ORIGINHosted page URL and its exact secure origin
NAT_EXPECTED_GATEWAY / NAT_EXPECTED_LOCAL_ADDRESSExact route for live discovery

The example public origin is https://example.com. Replace it with an origin you control and configure both the browser and peer consistently. Input workspaces retain their rc file and src/build result layout. Live SDK sources must match spike-sdk.rev exactly; this is a source prerequisite, not an available released-runtime claim. No key material belongs in committed files.

The offline suite uses fixtures and loopback sockets. Scripts that launch a phone window, inspect a real gateway or prepare a firewall rule are separate live experiments. Inspect their configuration before running them.