pixie / docs
SOURCE GUIDE GitHub ↗
How it works

The runtime features.

Configuration, TLS, concurrency, and logs.

Feature: configuration

src/config.rs selects a YAML, TOML, or JSON parser from the file extension. Compiled defaults cover missing values. An explicit TLS section requires a certificate and key. Configuration is loaded once at startup. See the format examples and option reference.

Feature: TLS and mTLS

src/tls.rs loads the PEM chain and private key into a rustls server config. Without a client CA it authenticates the server only. With a client CA it uses WebPkiClientVerifier to require a trusted client certificate. Credentials are loaded once, and async TLS handshakes run per connection. ALPN negotiates HTTP/2 or HTTP/1.1. Experimental HTTP/3 uses a separate QUIC UDP listener and also requires TLS.

Feature: worker pool

src/server.rs creates a Tokio multi-thread runtime using the configured worker count. Connections are asynchronous tasks; they do not reserve one runtime thread while waiting for network I/O. There is no explicit connection admission limit.

Feature: logging

src/logger.rs sends info, warning, and error messages to stderr. Startup logs show the address, worker count, TLS mode, and web root. There is no structured per-request access log or metrics endpoint yet.

Pixie documentation Built from the source. Updated with the features.