From 2bf5d0074cbb4ff387f48ea615cebcc91d7e69ad Mon Sep 17 00:00:00 2001 From: Greg Price Date: Tue, 23 Jan 2018 09:15:03 -0800 Subject: [PATCH] docs: Update ETA for Let's Encrypt wildcard support. It's now January 2018, so we can delete this caveat, right? Not quite yet -- the original post we link to now has an update saying 2018-02-27. Let's make it less specific, in case the date changes again. --- docs/production/ssl-certificates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/production/ssl-certificates.md b/docs/production/ssl-certificates.md index 9f848c3e58..4167999813 100644 --- a/docs/production/ssl-certificates.md +++ b/docs/production/ssl-certificates.md @@ -31,7 +31,7 @@ else if: * you have an existing workflow for managing SSL certificates that you prefer; * you need wildcard certificates (support from Let's Encrypt planned - for [January 2018][letsencrypt-wildcard]); or + for [early 2018][letsencrypt-wildcard]); or * your Zulip server is not on the public Internet. (In this case you can [still use Certbot][certbot-manual-mode], but it's less convenient; and you'll want to ignore Zulip's automation.)