acme_proxy_core/lib.rs
1//! The bottom of acme-proxy's crate graph: what every layer above it speaks.
2//!
3//! Configuration ([`config`]), the ACME wire vocabulary ([`identifier`],
4//! [`jws`], [`error`]'s problem documents, [`routes`]), the nested-JWS
5//! surfaces that are pure verification ([`eab`], [`key_change`]), certificate
6//! parsing ([`cert`]), the audit trail's vocabulary ([`audit`]), where a
7//! request came from ([`client`]), and the small shared helpers
8//! ([`datetime`], [`logfields`], [`palette`], [`pemfile`], [`random`],
9//! [`script_hook`], [`templating`]).
10//!
11//! Nothing here opens a database, dials a network or knows a signer; the
12//! crates that do are built on it. An internal crate of the `acme-proxy`
13//! binary, published in lockstep with it and with no semver promise of its
14//! own.
15
16pub mod audit;
17pub mod cert;
18pub mod client;
19pub mod config;
20pub mod datetime;
21pub mod eab;
22pub mod error;
23pub mod identifier;
24pub mod jws;
25pub mod key_change;
26pub mod logfields;
27pub mod palette;
28pub mod pemfile;
29pub mod random;
30pub mod routes;
31pub mod script_hook;
32pub mod templating;
33#[cfg(any(test, feature = "test-util"))]
34pub mod testutil;