mirror of https://github.com/zulip/zulip.git
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.
This commit is contained in:
parent
9a8d0ca9fe
commit
1c1c47b94a
|
@ -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
|
statistics, you can disable this feature at any time by setting
|
||||||
`SUBMIT_USAGE_STATISTICS=False` in `/etc/zulip/settings.py`.
|
`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
|
## Sending push notifications directly from your server
|
||||||
|
|
||||||
This section documents an alternative way to send push notifications
|
This section documents an alternative way to send push notifications
|
||||||
|
|
Loading…
Reference in New Issue