StackExchange/dnscontrol
1
1
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2024-12-27 18:51:49 +08:00
Code Issues Projects Releases Packages Wiki Activity

more typos

Browse source
This commit is contained in:
Craig Peterson 2018-04-26 15:36:39 -04:00
parent 5618442830
commit 9eab281513
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/lets-encrypt.md
View file

@ -106,11 +106,11 @@ The working directory should generally contain:
- `-acme {url}`: URL of the acme server you wish to use. For *Let's Encrypt* you can use the presets `live` or `staging` for the standard services. If you are using a custom boulder instance or other acme server, you may specify the full **directory** url. Must be an acme **v2** server.
- `-renew {n}`: `get-certs` will renew certs with less than this many **days** remaining. The default is 15, and certs will be renewed when they are within 15 days of expiration.
- `-dir {d}`: Root directory holding all certificate and account data as described above. Default is current woriking directory.
- `-dir {d}`: Root directory holding all certificate and account data as described above. Default is current working directory.
- `-certConfig {j}`: Location of certificate config json file as described above. Default is `./certs.json`
- `-skip {p}`: DNS Provider names (comma separated) to skip using as challenge providers. We use this to avoid uneccessary changes to our backup or internal dns providers that wouldn't be a part of the validation flow.
- `-skip {p}`: DNS Provider names (comma separated) to skip using as challenge providers. We use this to avoid unnecessary changes to our backup or internal dns providers that wouldn't be a part of the validation flow.
- `--verbose`: enable some extra logging from the [acme library](https://github.com/xenolf/lego) that we use.
- `-js {dnsconfig.js}`, `-creds {creds.json}` and other flags to find your dns configuration are the same as used for `dnscontrol preview` or `push`. `get-certs` needs to read the dns config so it knows which providers manage which domains, and so it can make sure it is not going to make any destructive changes to your domains. If the `get-certs` command needs to fill a challenge on a domain that has pending corrections, it will abort for safety. You can run `dnscontrol preview` and `dnscontrol push` at that point to cerify and push the pending corrrections, and then proceed with issuing certificates.
- `-js {dnsconfig.js}`, `-creds {creds.json}` and other flags to find your dns configuration are the same as used for `dnscontrol preview` or `push`. `get-certs` needs to read the dns config so it knows which providers manage which domains, and so it can make sure it is not going to make any destructive changes to your domains. If the `get-certs` command needs to fill a challenge on a domain that has pending corrections, it will abort for safety. You can run `dnscontrol preview` and `dnscontrol push` at that point to verify and push the pending corrections, and then proceed with issuing certificates.
## Workflow
@ -118,7 +118,7 @@ This command is intended to be just a small part of a full certificate automatio
This command is intended to be run as frequently as you desire. One workflow would be to check all certificates into a git repository and run a nightly build that:
1. Clones the cert repo, and the dns config repo (if seperate).
1. Clones the cert repo, and the dns config repo (if separate).
2. Decrypt or otherwise obtain the *Let's Encrypt* account private key. Dnscontrol does not need to read any certificate private keys to check or issue certificates.
3. Run `dnscontrol get-certs` with appropriate flags.
4. Encrypt or store any new or updated private keys.