aipper/mkcert
1
0
Fork 0
mirror of https://github.com/FiloSottile/mkcert.git synced 2025-10-14 00:41:40 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add keyless install only mode

Browse Source
This commit is contained in:
Filippo Valsorda
2018-06-26 01:14:57 -04:00
parent 6a3cad1731
commit 7433af8d0b
2 changed files with 19 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -43,13 +43,17 @@ $ cd mkcert && make
Windows will be supported soon.
## Changing the location of the CA files
## Advanced topics
TODO
### Changing the location of the CA files
## Installing the CA on other computers
The CA certificate and its key are stored in an application data folder in the user home. You usually don't have to worry about it, as installation is automated, but if you need it it's printed in the first line of the mkcert output.
TODO
If you want to manage separate CAs, you can use the environment variable `CAROOT` to set the folder where mkcert will place and look for the local CA files.
### Installing the CA on other computers
Installing in the trust store does not require the CA key, so you can export just the `rootCA.pem` file, point `CAROOT` to its directory on a different machine and run `-install`. Or, for example, commit just `rootCA.pem` and not its key to version control.
Remember that mkcert is meant for development purposes, not production, so it should not be used on users' machines.