Updated Notify_ntfy (markdown)

master
Chris Caron 2022-04-19 12:53:00 -04:00
parent ef7c698da1
commit 719aa24021
1 changed files with 7 additions and 0 deletions

@ -33,6 +33,13 @@ You can specify more then 1 topic such as:
| port | No | The port the ntfy server is listening on. By default the port is **80** for **ntfy://** and **443** for all **ntfys://** references.
| topic | Yes | All notifications to a ntfy server MUST have at least one topic defined.
| mode | No | The authentication mode is automatically detected based what it parses from the URL provided. You only need to set this if you feel it is being detected incorrectly. The possible modes are **private** and **cloud** and are explained above.
| email | No | An email to associate the ntfy post with.
| tags | No | The ntfy tags to associate with the ntfy post. Use a comma and/or space to specify more then one.
| attach | No | Specify a web URL pointing at a remote attachment you would like the post to reference.
| filename | No | This is only used if the `attach` was also provided. The ntfy server is smart enough to determine what the `filename` is automatically from this; however if you wish to provide a custom-override to this value, this is where you do it from.
| click | No | Provide a hyperlink that you want users who receive your notification to advance to if they click on it.
| priority | No | Provide a priority such as `max`, `high`, `default`, `low`, or `min`. By default `default` is used if one isn't otherwise provided.
| delay | No | Identify a delay for the message reception
#### Example
Send a ntfy notification to our server