Expand description
Infrastructure shared by Rushls and its sibling services.
Each module sits behind a feature of the same name, so a dependent compiles only what it uses. None of them choose application policy: they load configuration, talk to operator-configured services, terminate TLS, and accept connections, and leave reporting to the application’s own events.
Modules§
- accept
- What an accept loop does when
acceptfails. - config
- One loading contract for application-owned
conf::Confschemas. - hooks
- Telling other systems what happened, without ever slowing this one down.
- metrics
- Small, transport-independent pieces shared by metrics endpoints.
- outbound
- Requests this node makes to services an administrator configured.
- proxy_
protocol - PROXY protocol headers, read ahead of a TCP stream.
- tls
- TLS termination with certificates that rotate underneath a running origin.