move acmed to examples so it isn't automatically installed

Signed-off-by: Erik Hollensbe <git@hollensbe.org>
This commit is contained in:
Erik Hollensbe 2022-02-17 02:56:38 -08:00
parent efd5dd9902
commit e940f7eac8
No known key found for this signature in database
GPG key ID: 4BB0E241A863B389
3 changed files with 3 additions and 3 deletions

View file

@ -46,6 +46,6 @@ webpki-roots = "^0.22"
[lib] [lib]
[[bin]] [[example]]
name = "acmed" name = "acmed"
path = "src/acmed.rs" path = "examples/acmed.rs"

View file

@ -18,7 +18,7 @@ coyote is intended to let you build an `acmed` without using `acmed` itself, but
## Running `acmed` ## Running `acmed`
[acmed](src/acmed.rs) is a very small, example implementation of coyote, intended to demonstrate usage of it. It is not meant or designed to be used in a production environment. It does not perform challenges properly, allowing all of them that come in. [acmed](examples/acmed.rs) is a very small, example implementation of coyote, intended to demonstrate usage of it. It is not meant or designed to be used in a production environment. It does not perform challenges properly, allowing all of them that come in.
You'll need `docker` to launch the postgres instance. Provide `HOSTNAME` to set a host name for TLS service; otherwise `localhost` is assumed. A CA at `ca.pem` and `ca.key` will be generated at the directory you run the `cargo` commands from, which you will need to pass to clients to your certificates. Also, a TLS in-memory cert will be generated to serve the `acmed` instance. You'll need `docker` to launch the postgres instance. Provide `HOSTNAME` to set a host name for TLS service; otherwise `localhost` is assumed. A CA at `ca.pem` and `ca.key` will be generated at the directory you run the `cargo` commands from, which you will need to pass to clients to your certificates. Also, a TLS in-memory cert will be generated to serve the `acmed` instance.