sova-acme 0.1.1

Let's Encrypt ACME (HTTP-01) certificates for Sova with TLS hot-reload
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39

[![crates.io](https://img.shields.io/crates/v/sova-acme?style=for-the-badge)](https://crates.io/crates/sova-acme)
[![docs.rs](https://img.shields.io/docsrs/sova-acme?style=for-the-badge)](https://docs.rs/sova-acme)
[![License](https://img.shields.io/crates/l/sova-acme?style=for-the-badge)](https://github.com/s00d/sova/blob/master/LICENSE)

# sova-acme

Let's Encrypt **HTTP-01** certificates for Sova with **TLS hot-reload** (no process restart).

**Guide:** [https://s00d.github.io/sova/plugins/acme](https://s00d.github.io/sova/plugins/acme)

```bash
cargo add sova --features "tls,acme"
```

```rust
use sova::{Acme, App, Result};

#[tokio::main]
async fn main() -> Result<()> {
    let mut app = App::new();
    app.get("/", || async { "hello https" });
    app.install(
        Acme::lets_encrypt(["example.com"])
            .email("ops@example.com")
            .dir("./data/acme")
            .hsts(true),
    );
    // install attached TLS to the app — just listen
    app.listen(443).await
}
```

Port **80** must be reachable for HTTP-01. The plugin listens there for challenges and (by default) redirects other traffic to HTTPS. Use `.staging(true)` / `Acme::lets_encrypt_staging` while testing.

CLI: `acme status` / `acme renew` (force). Events: `CertificateIssued`, `CertificateRenewed`, `AcmeFailed`.

## License

MIT — see [LICENSE](LICENSE).