Auto merge of #3436 - Turbo87:civet, r=jtgeibel

Remove `civet` server option

as discussed in our weekly team meeting today :)

Resolves #2204

Author: bors

Cargo.lock

@@ -34,7 +34,6 @@ anyhow = "1.0"
 base64 = "0.13"
 cargo-registry-s3 = { path = "src/s3", version = "0.2.0" }
 chrono = { version = "0.4.0", features = ["serde"] }
-civet = "0.12.0-alpha.5"
 clap = "=3.0.0-beta.2"
 comrak = { version = "0.9", default-features = false }
 
@@ -48,7 +47,6 @@ conduit-router = "0.9.0-alpha.6"
 conduit-static = "0.9.0-alpha.3"
 
 cookie = { version = "0.15", features = ["secure"] }
-ctrlc = { version = "3.0", features = ["termination"] }
 dashmap = { version = "4.0.2", features = ["raw-api"] }
 derive_deref = "1.1.1"
 dialoguer = "0.7.1"

Cargo.toml

@@ -12,11 +12,10 @@ The server does the following things:
 3. Reads values from environment variables to configure a new instance of `cargo_registry::App`
 4. Adds middleware to the app by calling `cargo_registry::middleware`
 5. Syncs the categories defined in *src/categories.toml* with the categories in the database
-6. Starts either a [conduit] or a [hyper] server that uses the `cargo_registry::App` instance
+6. Starts a [hyper] server that uses the `cargo_registry::App` instance
 7. Tells Nginx on Heroku that the application is ready to receive requests, if running on Heroku
 8. Blocks forever (or until the process is killed)
 
-[civet]: https://crates.io/crates/civet
 [hyper]: https://crates.io/crates/hyper
 
 ## Routes