|
@@ -52,17 +52,17 @@ Warning: the `rootCA-key.pem` file that mkcert automatically generates gives com
|
|
|
|
|
|
### Changing the location of the CA files
|
|
|
|
|
|
-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.
|
|
|
+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 by `mkcert -CAROOT`.
|
|
|
|
|
|
-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.
|
|
|
+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 systems
|
|
|
|
|
|
Installing in the trust store does not require the CA key, so you can export just the CA certificate and use mkcert to install it in other machines.
|
|
|
|
|
|
-* Look for the `rootCA.pem` file in `CAROOT` or in the default folder (see above)
|
|
|
+* Look for the `rootCA.pem` file in `mkcert -CAROOT`
|
|
|
* copy it to a different machine
|
|
|
-* set `CAROOT` to its directory
|
|
|
+* set `$CAROOT` to its directory
|
|
|
* run `mkcert -install`
|
|
|
|
|
|
Remember that mkcert is meant for development purposes, not production, so it should not be used on end users' machines, and that you should *not* export or share `rootCA-key.pem`.
|