github
/
apprise
mirror of https://github.com/caronc/apprise
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated config (markdown)

master
Chris Caron 2022-04-19 13:14:00 -04:00
parent 8119a44acb
commit 8ae8a48457
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
config.md

@ -149,7 +149,7 @@ apprise -b "has (TagA AND TagB) OR TagC" --tag="TagA, TagB" --tag=TagC
The following special tags are reserved for use
| Tag | Usage | Description |
| --------------- | -------- |------------- |
| `always` | config | If you store an Apprise entry in a config file and associate the `always` tag with it, it will **ALWAYS** be notified reguardless of any tagging restriction you place on the CLI
| `always` | config | If you store an Apprise entry in a config file and associate the `always` tag with it, it will **ALWAYS** be notified regardless of any tagging restriction you place on the CLI
| `all` | notifications | When performing a notification, you always have the ability to filter which services are notified based on the tags you've assigned them. However if you perform a notification and indicate that you want to notify and are filtering on the `all` tag, absolutely everything will be notified (regardless of what other tags have been assigned to it).
It's also worth noting that if you do not assign a tag to an Apprise configuration entry, it can only be actioned/notified if the call to Apprise also does not identify a tag to filter on. However un-tagged configuration entries will be always included in `all` references.