From 653f121192337e3b53fa41b90f2f33e65af0bf0a Mon Sep 17 00:00:00 2001 From: AJ ONeal Date: Wed, 1 Feb 2017 15:56:40 -0700 Subject: [PATCH] change --servername to --sites --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 4fc13ce..27ed2e5 100644 --- a/README.md +++ b/README.md @@ -58,7 +58,7 @@ Examples: npm install -g git+https://git@git.daplie.com:Daplie/serve-https # Use tunnel -serve-https --servername jane.daplie.me --agree-tos --email jane@example.com --tunnel +serve-https --sites jane.daplie.me --agree-tos --email jane@example.com --tunnel # BEFORE you access in a browser for the first time, use curl # (because there's a concurrency bug in the greenlock setup) @@ -75,8 +75,8 @@ Options: * `--email ` - email to use for Let's Encrypt, Daplie DNS, Daplie Tunnel * `--agree-tos` - agree to terms for Let's Encrypt, Daplie DNS -* `--servername ` - use `` instead of `localhost.daplie.me` -* `--tunnel` - make world-visible (must use `--servername`) +* `--sites ` - use `` instead of `localhost.daplie.me` +* `--tunnel` - make world-visible (must use `--sites`) Specifying a custom HTTPS certificate: @@ -93,7 +93,7 @@ Note: `--root` may specify single cert or a bundle, and may be used multiple tim Other options: * `--serve-root true` alias for `-c` with the contents of root.pem -* `--servername example.com` changes the servername logged to the console +* `--sites example.com` changes the servername logged to the console * `--letsencrypt-certs example.com` sets and key, fullchain, and root to standard letsencrypt locations Examples @@ -139,7 +139,7 @@ which is equilavent to ```bash sudo serve-https -p 8443 \ - --servername test.mooo.com + --sites test.mooo.com --key /etc/letsencrypt/live/test.mooo.com/privkey.pem \ --cert /etc/letsencrypt/live/test.mooo.com/fullchain.pem \ --root /etc/letsencrypt/live/test.mooo.com/root.pem \