Skip to content

Commit a65bf57

Browse files
authored
Merge pull request alexjustesen#101 from svenvg93/apprise-improve
Small improvments to the apprise docs
2 parents 104e63d + b250476 commit a65bf57

File tree

2 files changed

+21
-5
lines changed

2 files changed

+21
-5
lines changed
-57.2 KB
Binary file not shown.

settings/notifications/apprise.md

Lines changed: 21 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,32 @@
22

33
Apprise provides a unified notification channel that lets you send alerts to numerous services—like Discord, Pushover, and Ntfy as well as many additional platforms
44

5-
<figure><img src="../../.gitbook/assets/apprise_notifiations.png" alt=""><figcaption><p>Apprise settings</p></figcaption></figure>
5+
### Why Apprise
6+
7+
Apprise allows the application to sent notifications to a wide variety of services. It let us focus on features instead of maintaining X number of notification channels. Essentially helping us cut down on maintenance/feature requests.
68

79
### Apprise Server
810

9-
To use Apprise, you’ll need to set up your own Apprise container. This container isn’t created automatically, so make sure to include it in your deployment. See the Apprise [Github Repo](https://github.com/caronc/apprise-api) for the setup instructions.
11+
To use Apprise, you’ll need to set up your own Apprise instance. This container isn’t created automatically, so make sure to include it in your deployment. See the Apprise [Github Repo](https://github.com/caronc/apprise-api) for the setup instructions. On the notification page you will need to define the location of your Apprise instance. Make sure this instance is reachable for the Speedtest Tracker.
12+
13+
{% hint style="info" %}
14+
We don't offer support on setting up Apprise, incase of any problems with the Apprise Container please reach out to the Apprise team.&#x20;
15+
{% endhint %}
16+
17+
### Notification Channels
18+
19+
Notification channels are the formatted URLs used by Apprise to send notifications to various services. Refer to the [Apprise documentation](https://github.com/caronc/apprise?tab=readme-ov-file#supported-notifications) for a full list of supported channels and their required formats. You can add as many different channels as you wish. The notifications will be sent to all of them.&#x20;
20+
21+
### Tips and Tricks
22+
23+
#### Format
24+
25+
By default the format used for message is `markdown` This allows us to do some formatting on the message like bold text etc.
1026

11-
### Apprise Channels
27+
#### Preview Images
1228

13-
Apprise channels are the formatted URLs used by Apprise to send notifications to various services. Refer to the [Apprise documentation](https://github.com/caronc/apprise?tab=readme-ov-file#supported-notifications) for a full list of supported channels and their required formats.
29+
By default Apprise does not allow preview images for URLs. This is an default setting on the Apprise instance. Depending on the service used you can override this settings in the notification channel URL. Check the Apprise documentation to see if your service support this and how to set it.&#x20;
1430

1531
### Triggers
1632

17-
<table><thead><tr><th width="237">Name</th><th>Description</th></tr></thead><tbody><tr><td>on every scheduled speedtest run</td><td>On each successful scheduled speedtest a notification will be send to the application.</td></tr><tr><td>on threshold failures for scheduled speedtests</td><td>On any absolute threshold failure for scheduled speedtest a notification will be send to the application.</td></tr></tbody></table>
33+
<table><thead><tr><th width="237">Name</th><th>Description</th></tr></thead><tbody><tr><td>on every scheduled speedtest run</td><td>On each successful scheduled speedtest a notification will be send to the application.</td></tr><tr><td>on threshold failures for scheduled speedtests</td><td>On any absolute threshold failure for scheduled speedtest a notification will be send to the application.</td></tr></tbody></table>

0 commit comments

Comments
 (0)