Homebrew and usage

This commit is contained in:
Filippo Valsorda
2018-06-26 00:39:02 -04:00
parent c59b5d9d13
commit 6a3cad1731
3 changed files with 39 additions and 5 deletions

View File

@@ -20,18 +20,18 @@ Created a new certificate valid for the following names 📜
The certificate is at "./example.com+4.pem" and the key at "./example.com+4-key.pem" ✅
```
![Chrome screenshot](https://user-images.githubusercontent.com/1225294/41887838-7acd55ca-78d0-11e8-8a81-139a54faaf87.png)
<p align="center"><img width="444" alt="Chrome screenshot" src="https://user-images.githubusercontent.com/1225294/41887838-7acd55ca-78d0-11e8-8a81-139a54faaf87.png"></p>
Obtaining certificates from real 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 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.
mkcert automatically creates and installs a local CA in the system root store, and generates locally-trusted certificates for any hosts.
mkcert automatically creates and installs a local CA in the system root store, and generates locally-trusted certificates.
## Installation
On macOS, use Homebrew.
```
TODO
brew install --HEAD FiloSottile/mkcert/mkcert
```
On Linux, use [the pre-built binaries](https://github.com/FiloSottile/mkcert/releases), or build from source.