From 1c1c47b94aa2076131cf99562a98800e31a4522e Mon Sep 17 00:00:00 2001 From: Tim Abbott Date: Tue, 5 May 2020 15:59:35 -0700 Subject: [PATCH] docs: Delete discussion of legacy push notifications signup. This hasn't been used in months; it was only there in case of problems with the rollout of the automated workflow, so it makes sense to delete it now. --- docs/production/mobile-push-notifications.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/docs/production/mobile-push-notifications.md b/docs/production/mobile-push-notifications.md index 66f95c09ef..d2d1c1b443 100644 --- a/docs/production/mobile-push-notifications.md +++ b/docs/production/mobile-push-notifications.md @@ -163,19 +163,6 @@ itself. If your organization does not want to submit these statistics, you can disable this feature at any time by setting `SUBMIT_USAGE_STATISTICS=False` in `/etc/zulip/settings.py`. -## Legacy signup - -Here are legacy instructions for signing a server up for push -notifications, for Zulip 1.8 and older. - -1. First, contact support@zulipchat.com with the `zulip_org_id` and - `zulip_org_key` values from your `/etc/zulip/zulip-secrets.conf` file, as - well as a `hostname` and `contact email` address you'd like us to use in case - of any issues (we hope to have a nice web flow available for this soon). - -2. We'll enable push notifications for your server on our end. Look for a - reply from Zulipchat support within 24 hours. - ## Sending push notifications directly from your server This section documents an alternative way to send push notifications