Refactoring the README.
Cleaned up:
- Spelling
- Grammar
- Formatting
Doing my part to help out the maintainer of this awesome tool! Thank you @neilpang
The parameter `/home/wwwroot/aa.com` is the web root folder, You must have `write` access to this folder.
The parameter `/home/wwwroot/aa.com` is the web root folder. You **MUST** have `write access` to this folder.
Second argument "aa.com" is the main domain you want to issue cert for.
You must have at least domain there.
Second argument **"aa.com"** is the main domain you want to issue cert for.
You must have at least a domain there.
You must point and bind all the domains to the same webroot dir:`/home/wwwroot/aa.com`
You must point and bind all the domains to the same webroot dir:`/home/wwwroot/aa.com`.
The cert will be placed in `~/.acme.sh/aa.com/`
Generate/issued certs will be placed in `~/.acme.sh/aa.com/`
The issued cert will be renewed every 80 days automatically.
The issued cert will be renewed every 80 days automatically.
More examples: https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert
More examples: https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert
# Install issued cert to apache/nginx etc.
# Install issued cert to apache/nginx etc.
After you issue a cert, you probably want to install the cert to your nginx/apache or other servers to use.
```
acme.sh --installcert -d aa.com \
After you issue a cert, you probably want to install the cert with your nginx/apache or other servers you may be using.
```bash
acme.sh --installcert -d aa.com \
--certpath /path/to/certfile/in/apache/nginx \
--certpath /path/to/certfile/in/apache/nginx \
--keypath /path/to/keyfile/in/apache/nginx \
--keypath /path/to/keyfile/in/apache/nginx \
--capath /path/to/ca/certfile/apache/nginx \
--capath /path/to/ca/certfile/apache/nginx \
@ -184,43 +195,48 @@ Only the domain is required, all the other parameters are optional.
Install the issued cert/key to the production apache or nginx path.
Install the issued cert/key to the production apache or nginx path.
The cert will be renewed every 80 days by default (which is configurable), Once the cert is renewed, the apache/nginx will be automatically reloaded by the command: `service apache2 reload` or `service nginx reload`
The cert will be `renewed every 80 days by default` (which is configurable). Once the cert is renewed, the apache/nginx will be automatically reloaded by the command: `service apache2 reload` or `service nginx reload`.
# Use Standalone server to issue cert
# Use Standalone server to issue cert
(requires you be root/sudoer, or you have permission to listen tcp 80 port):
Same usage as all above, just give `no` as the webroot.
The tcp `80` port must be free to listen, otherwise you will be prompted to free the `80` port and try again.
If your dns provider is not in the supported list above, you can write your own script api easily.
If your DNS provider is not on the supported list above, you can write your own script API easily. If you do please consider submitting a [Pull Request](https://github.com/Neilpang/acme.sh/pulls) and contribute to the project.
For more details: [How to use dns api](dnsapi)
For more details: [How to use dns api](dnsapi)
# Issue ECC certificate:
# Issue ECC certificate:
LetsEncrypt now can issue ECDSA certificate.
`Let's Encrypt` now can issue **ECDSA** certificates.
And we also support it.
And we also support it.
Just set the `length` parameter with a prefix `ec-`.
Just set the `length` parameter with a prefix `ec-`.
Sergei Filippov
9 years ago