coolaj86/greenlock-cli.js
1
0
Fork 0
Code Issues 4 Pull Requests Releases Activity

Update README.md

Browse Source
This commit is contained in:
AJ ONeal 2015-12-16 05:02:09 -08:00
parent 7c1f17c818
commit 5231bb9401
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -45,19 +45,20 @@ letsencrypt certonly \
--domains example.com,www.example.com \
--server https://acme-staging.api.letsencrypt.org/directory \
ls ~/letsencrypt/etc
ls ~/letsencrypt/etc/live
```
### WebRoot
```bash
letsencrypt certonly \
sudo letsencrypt certonly \
--agree-tos --email john.doe@example.com \
--webroot --webroot-path /srv/www/acme-challenge \
--config-dir /etc/letsencrypt \
--domains example.com,www.example.com \
--server https://acme-staging.api.letsencrypt.org/directory
ls ~/letsencrypt/etc
ls /etc/letsencrypt/live/
```
## Run without Root
@ -70,6 +71,15 @@ you can use `setcap` to do so. (it may need to be run any time you reinstall nod
sudo setcap cap_net_bind_service=+ep /usr/local/bin/node
```
By default `node-letsencrypt` assumes your home directory `~/letsencrypt/`, but if
you really want to use `/etc/letsencrypt`, `/var/lib/letsencrypt/`, and `/var/log/letsencrypt`
you could change the permissions on them. **Probably a BAD IDEA**. Probabry a security risk.
```
# PROBABLY A BAD IDEA
sudo chown -R $(whoami) /etc/letsencrypt /var/lib/letsencrypt /var/log/letsencrypt
```
## Command line Options
```