From bf089257905a02f86224f018e2b698996fd28480 Mon Sep 17 00:00:00 2001 From: Filippo Valsorda Date: Sun, 19 May 2019 14:11:53 -0400 Subject: [PATCH] README: mention "example.test" as an example --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2924fa5..f77b0ab 100644 --- a/README.md +++ b/README.md @@ -24,7 +24,7 @@ The certificate is at "./example.com+5.pem" and the key at "./example.com+5-key.

Chrome and Firefox screenshot

-Using certificates from real certificate authorities (CAs) for development can be dangerous or impossible (for hosts like `localhost` or `127.0.0.1`), but self-signed certificates cause trust errors. Managing your own CA is the best solution, but usually involves arcane commands, specialized knowledge and manual steps. +Using certificates from real certificate authorities (CAs) for development can be dangerous or impossible (for hosts like `example.test`, `localhost` or `127.0.0.1`), but self-signed certificates cause trust errors. Managing your own CA is the best solution, but usually involves arcane commands, specialized knowledge and manual steps. mkcert automatically creates and installs a local CA in the system root store, and generates locally-trusted certificates. mkcert does not automatically configure servers to use the certificates, though, that's up to you.