Trim unused axum/tower-http features; 'deploying', not 'self-hosting'

Cargo.lock

@@ -9557,7 +9557,6 @@ dependencies = [
  "tower 0.5.2",
  "tower-layer",
  "tower-service",
- "tracing",
  "url",
 ]
 

crates-server/yaak-send-proxy/Cargo.toml

@@ -18,7 +18,7 @@ path = "src/main.rs"
 
 [dependencies]
 async-trait = "0.1"
-axum = { version = "0.7", features = ["http1", "http2", "json", "tokio"] }
+axum = "0.7"
 base64 = "0.22.1"
 bytes = "1.11.1"
 clap = { version = "4.5", features = ["derive", "env"] }
@@ -28,7 +28,7 @@ log = { workspace = true }
 serde = { workspace = true, features = ["derive"] }
 serde_json = { workspace = true }
 tokio = { workspace = true, features = ["rt-multi-thread", "macros", "signal", "sync", "io-util", "time", "net"] }
-tower-http = { version = "0.6", features = ["cors", "trace"] }
+tower-http = { version = "0.6", features = ["cors"] }
 ts-rs = { workspace = true }
 url = "2"
 uuid = { version = "1", features = ["v4"] }

crates-server/yaak-send-proxy/README.md

@@ -65,9 +65,9 @@ Refusals are logged with the reason. There is no switch to turn this off: the
 proxy's private network is the cloud's, not the user's, so a `localhost` or LAN
 API can never be reached through it — that is what the desktop app is for.
 
-## Self-hosting
+## Deploying
 
-One binary, no dependencies. Build it and run it wherever you like:
+One binary, no dependencies:
 
 ```shell
 cargo build --release -p yaak-send-proxy

crates-server/yaak-send-proxy/src/main.rs

@@ -7,7 +7,7 @@
 //! for the tab to store. It keeps nothing: no database, no files, no session.
 //!
 //! One binary, configured by flags or `YAAK_PROXY_*` environment variables.
-//! See README.md for running and self-hosting it, and `guard.rs` for what it
+//! See README.md for running and deploying it, and `guard.rs` for what it
 //! refuses to talk to.
 
 mod config;