-
-
Notifications
You must be signed in to change notification settings - Fork 440
Notify_gotify
Chris Caron edited this page Mar 13, 2019
·
9 revisions
- Source: https://github.com/gotify/server
- Icon Support: No
- Message Format: Text
- Message Limit: 32768 Characters per Message
Valid syntaxes are as follows:
- gotify://@{hostname}/{token}
- gotifys://@{hostname}/{token}
- gotifys://@{hostname}:{port}/{token}
- gotifys://@{hostname}/{token}/?priority=high
Secure connections (via https) should be referenced using gotifys:// where as insecure connections (via http) should be referenced via gotify://.
Variable | Required | Description |
---|---|---|
hostname | Yes | The Rocket.Chat server you're sending your notification to. |
token | Yes | The Application Token you generated on your Gotify Server |
port | No | The port the Gotify server is listening on. By default the port is 80 for gotify:// and 443 for all gotifys:// references. |
priority | No | The priority level to pass the message along as. Possible values are low, moderate, normal, and high. If no priority is specified then normal is used. |
Send a Gotify message:
# Assuming our {hostname} is localhost
# Assuming our {token} is abcdefghijklmn
apprise gotify://rocket.server.local/abcdefghijklmn
Here is how I set up a quick Gotify server to test against. This may or may not be useful to other people.
Based on this source:
# Docker (assuming a connection to docker.io)
sudo docker pull gotify/server
sudo docker run -p 80:80 -v /var/gotify/data:$(pwd)/data gotify/server
# Then visit http://localhost