Expand description
API server assembly, lifecycle, and readiness.
startup binds the TCP listener before bootstrap and serves a starting
health probe; builder composes the full axum router and global
middleware stack; runner runs the startup reconciliation, swaps the
full router onto the listener, and awaits shutdown. The readiness
signalling surface (is_ready, signal_ready, wait_for_ready) is
used by external health probes. Discovery, health, metrics, and route
configuration live in the private submodules.
Copyright (c) systemprompt.io — Business Source License 1.1. See https://systemprompt.io for licensing details.
Re-exports§
pub use readiness::ReadinessEvent;pub use readiness::get_readiness_receiver;pub use readiness::init_readiness;pub use readiness::is_ready;pub use readiness::signal_ready;pub use readiness::signal_shutdown;pub use readiness::wait_for_ready;pub use startup::EarlyServer;pub use startup::bind_and_serve;pub use startup::starting_router;pub use builder::*;pub use runner::*;
Modules§
- builder
- Full API router construction and the global middleware stack.
- metrics
- Prometheus recorder installation and HTTP metrics rendering.
- readiness
- Process-wide readiness flag and readiness-event broadcast.
- runner
- Server run loop: MCP orchestrator wiring and lifecycle supervision.
- scheduler_
health - Process-wide record of jobs the scheduler dropped at startup.
- startup
- Early-bind listener that answers health probes before bootstrap finishes.