CLI_Usage
This small tool wraps the apprise python library to allow individuals such as Developers, DevOps, and Administrators to send notifications from the command line.
Apprise in it's most basic form requires that you provide it a message and an Apprise URL which contains enough information to send the notification with. A list of supported services and how to build your own URL can be found here. Here is a simple email example:
# Set a notification to a hotmail (email) account:
apprise --body="My Message" mailto://user:[email protected]If you don't specify a --body (-b) then Apprise reads from stdin instead:
# without a --body, you can use a pipe | to redirect output
# into you're notification:
uptime | apprise mailto://user:[email protected]By default Apprise is very silent; If you want to have a better understanding of what is going on, just add a -v switch to improve the verbosity. The more v's you add, the more detailed output you'll get back.
There is no limit to the number of services you want to notify, just keep adding/chaining them one after another:
# Set a notification to a yahoo email account, Slack, and a Kodi Server
# with a bit of added verbosity (2 v's specified):
apprise -vv --body="Notify more than one service" \
mailto://user:[email protected] \
slack://token_a/token_b/token_c \
kodi://example.comAll of the switches and options available to you can be presented by adding --help (-h) to the command line:
# Print all of the help information:
apprise --helpThe switches/options are as follows:
Usage:
apprise [OPTIONS] [APPRISE_URL [APPRISE_URL2 [APPRISE_URL3]]]
apprise storage [OPTIONS] [ACTION] [UID1 [UID2 [UID3]]]
Send a notification to all of the specified servers identified by their URLs
the content provided within the title, body and notification-type.
For a list of all of the supported services and information on how to use
them, check out at https://github.com/caronc/apprise
Options:
-b, --body TEXT Specify the message body. If no body is
specified then content is read from <stdin>.
-t, --title TEXT Specify the message title. This field is
complete optional.
-P, --plugin-path PLUGIN_PATH Specify one or more plugin paths to scan.
-S, --storage-path STORAGE_PATH
Specify the path to the persistent storage
location
(default=~/.local/share/apprise/cache).
-SPD, --storage-prune-days INTEGER
Define the number of days the storage prune
should run using. Setting this to zero (0)
will eliminate all accumulated content. By
default this value is 30 (days).
-SUL, --storage-uid-length INTEGER
Define the number of unique characters to
store persistentcache in. By default this
value is 6 (characters).
-SM, --storage-mode MODE Persistent disk storage write mode
(default=auto). Possible values are "auto",
"flush", and "memory".
-c, --config CONFIG_URL Specify one or more configuration locations.
-a, --attach ATTACHMENT_URL Specify one or more attachment.
-n, --notification-type TYPE Specify the message type (default=info).
Possible values are "info", "success",
"warning", and "failure".
-i, --input-format FORMAT Specify the message input format
(default=text). Possible values are "text",
"html", and "markdown".
-T, --theme THEME Specify the default theme.
-g, --tag TAG Specify one or more tags to filter which
services to notify. Use multiple --tag (-g)
entries to "OR" the tags together and comma
separated to "AND" them. If no tags are
specified then all services are notified.
-Da, --disable-async Send all notifications sequentially
-d, --dry-run Perform a trial run but only prints the
notification services to-be triggered to
stdout. Notifications are never sent using
this mode.
-l, --details Prints details about the current services
supported by Apprise.
-R, --recursion-depth INTEGER The number of recursive import entries that
can be loaded from within Apprise
configuration. By default this is set to 1.
-v, --verbose Makes the operation more talkative. Use
multiple v to increase the verbosity. I.e.:
-vvvv
-e, --interpret-escapes Enable interpretation of backslash escapes
-j, --interpret-emojis Enable interpretation of :emoji: definitions
-D, --debug Debug mode
-V, --version Display the apprise version and exit.
-h, --help Show this message and exit.
Actions:
storage Access the persistent storage disk administration
list List all URL IDs associated with detected URL(s). This
is also the default action ran if nothing is provided
prune Eliminates stale entries found based on --storage-prune-
days (-SPD)
clean Removes any persistent data created by Apprise
Ideally it's never safe to store your personal details on the command line; others might see it! So the best thing to do is stick your configuration into a simple configuration file. With respect to the above example, maybe your file will look like this:
# use hashtag/pound characters to add comments into your
# configuration file. Define all of your URLs one after
# another:
mailto://user:[email protected]
slack://token_a/token_b/token_c
kodi://example.comThen you can notify all of your services like so:
# Set a notification to a yahoo email account, Slack, and a Kodi Server:
apprise -v --body="Notify more than one service" \
--config=/path/to/your/apprise/config.txtIf you stick your configuration in the right locations, you don't even need to reference the --config as it will be included automatically; the default filename paths are as follows:
-
Linux/Mac users:
~/.apprise~/.config/apprise
-
Microsoft Windows users:
%APPDATA%/Apprise/apprise%LOCALAPPDATA%/Apprise/apprise
With default configuration file(s) in place, reference to the Apprise CLI gets even easier:
# Set a notification to a yahoo email account, Slack, and a Kodi Server:
apprise -v --body="Notify all of my services"Apprise even lets you send file attachments to the services you use (provided they support them). Attachments are passed along by just including the --attach (-a) switch along with your Apprise command:
# Set a simple attachment:
apprise --title="A photo of my family" --body="see attached" \
--attach=/path/to/my/photo.jpeg
# You can attach as many file attachments as you like:
apprise -v --title="Several great photo's of the gang" --body="see attached" \
--attach=/path/team1.jpeg \
--attach=/path/teambuilding-event.jpg \
--attach=/path/paintball-with-office.jpgNote: When using attachments, if one of them can't be found/retrieved for delivery then the message isn't sent.
The great thing with attachments is that Apprise is able to make a remote web-request for them (prior to attaching them). This is easily done by just using the http:// or https:// protocol. This works great for things like security camera images, or just content you want to pass along hosted online:
# A web-based attachment:
apprise -v --title="A Great Github Cheatsheet" --body="see attached" \
--attach="https://github.github.com/training-kit/downloads/github-git-cheat-sheet.pdf"Consider the case where you've defined all of your Apprise URLs in one file, but you don't want to notify all of them each and every time.
- 📥 Maybe you have special notifications that only fire when a download completed.
- 🚨 Maybe you have home monitoring that requires you to notify several different locations
- 👷♂️ Perhaps you work as an Administrative, Developer, and/or Devops role and you want to just notify certain people at certain times (such as when a software build completes, or a unit test fails, etc).
Apprise makes this easy by simply allowing you to tag your URLs. There is no limit to the number of tags associate with a URL. Let's make a simple apprise configuration file; this can be done with any text editor of your choice:
# Tags in a Text configuration sit in front of the URL
# - They are comma and/or space separated (if more than one
# - To mark that you are no longer specifying tags and want to identify
# the URL, you just place an equal (=) sign and write the URL:
#
# Syntax: <tags>=<url>
# Here we set up a mailto:// URL and assign it the tags: me, and family
# maybe we are doing this to just identify our personal email and
# additionally tag ourselves with the family (which we will tag elsewhere
# too)
me,family=mailto://user:[email protected]
# Here we set up a mailto:// URL and assign it the tag: family
# In this example, we would email 2 people if triggered
family=mailto://user:[email protected]/[email protected]/[email protected]
# This might be our Slack Team Server targeting the #devops channel
# We assign it the tag: team
team=slack://token_a/token_b/token_c/#general
# Maybe our company has a special devops group too idling in another
# channel; we can add that to our list too and assign it the tag: devops
devops=slack://token_a/token_b/token_c/#devops
# Here we assign all of our colleagues the tags: team, and email
team,email=mailto://user:[email protected]/[email protected]/[email protected]/[email protected]
# Maybe we have home automation at home, and we want to notify our
# kodi box when stuff becomes available to it
mytv=kodi://example.com
# There is no limit... fill this file to your hearts content following
# the simple logic identified aboveNow there is a lot to ingest from the configuration above, but it will make more sense when you see how the content is referenced. Here are a few examples (based on config above):
# This would notify the first 2 entries they have the tag `family`
# It would 'NOT' send to any other entry defined
apprise -v --body="Hi guys, I'm going to be late getting home tonight" \
--tag=family
# This would only notify the first entry as it is the only one
# that has the tag: me
apprise -v --body="Don't forget to buy eggs!" \
--tag=meIf you're building software, you can set up your continuous integration to notify your team AND devops by simply identifying 2 tags:
# notify the services that have either a `devops` or `team` tag
# If you check our our configuration; this matches 3 separate URLs
apprise -v --title="Apprise Build" \
--body="Build was a success!" \
--tag=devops --tag=teamWhen you specify more than one --tag the contents are OR'ed together.
If you identify more than one element on the same --tag using a space and/or comma, then these get treated as an AND. Here is an example:
# notify only the services that have both a team and email tag
# In this example, there is only one match.
apprise -v --title="Meeting this Friday" \
--body="Guys, there is a meeting this Friday with our director." \
--tag=team,emailThere is a special reserved tag called all. all will match ALL of your entries regardless of what tag name you gave it. Use this with caution.
Here is another way of looking at it:
# assuming you got your configuration in place; tagging works like so:
apprise -b "has TagA" --tag=TagA
apprise -b "has TagA OR TagB" --tag=TagA --tag=TagB
# For each item you group with the same --tag value is AND'ed
apprise -b "has TagA AND TagB" --tag="TagA, TagB"
apprise -b "has (TagA AND TagB) OR TagC" --tag="TagA, TagB" --tag=TagCOnce you've built your elaborate configuration file and assigned all your tags. You certainly won't want to notify everyone over and over again while you test it out. Don't worry, that's what --dry-run (-d) is for. You can use this to test your tag logic out and not actually perform the notification.
# Test which services would have been notified if the tags team and email
# were activated:
apprise --title="Meeting this Friday" \
--body="Guys, there is a meeting this Friday with our director." \
--tag=team,email \
--dry-runIf you use the --dry-run (-d) switch, then some rules don't apply. For one, the --body (-b) is not even a required option. The above could have been re-written like so:
# Test which services would have been notified if the tags team and email
# were activated (without actually notifying them):
apprise --tag=team,email --dry-runApprise offers a lot of services at your fingertips, but some of them may or may not be available to you depending on your Operating system and/or what packages you have installed. You can see a list of what is available by doing the following:
# List all of the supported services available to you
# you can also use -l as well:
apprise --detailsHere is an example of the output (as it is now) on the CLI:
The Apprise CLI doesn't know what you are feeding it when sending a message to a Notification provider. It just assumes that whatever you message you feed it, it should just pass it along as is to the upstream provider as text. In most cases, this is perfect and this is the default behaviour. However, if you are passing along HTML content or markdown content, you should just let Apprise know by specifying the --input-format (-i) switch. For example:
# An HTML Example:
cat test.html | apprise --input-format=html
# Or Markdown:
cat << _EOF | apprise --input-format=markdown
## Ways to Prepare Eggs
* Scrambled
* Sunny Side Up
* Over Easy
There is more, but I want to keep my message short. :)
_EOFApprise now offers you the ability to pass in entries like :slightly_smiling_face: to have it automatically change this into a 🙂 unicode equivalent. Apprise is loaded with all of the emojis (and their mappings) as defined here
There are 2 ways to orchestrate the emoji engine and begin your translations:
-
Globally (impact all Apprise endpoints added):
# By default assume ?emojis=yes on all URLs # IF a URL is detected as having ?emojis=no, the no will trump and # no emoji mapping will be applied apprise --title=":+1: Great work everyone!" \ --body="So proud of you all! :rocket:." \ --interpret-emojis \ "myschema://credentials"
-
Per-Instance Basis:
# No use of the --interpret-emojis (-j) flag, however explicit # reference on the URL we're notifying. apprise --title=":+1: Great work everyone!" \ --body="So proud of you all! :rocket:." \ "myschema://credentials?emojis=yes"
Emojis offer a more rich use of Apprise. The above example would have passed the following to all upstream services:
- title: 👍 Great work everyone!
- body: So proud of you all! 🚀.
Users of Tmux can link their alert-bell to use Apprise like so:
# set your tmux bell-action to type 'other':
set-option -g bell-action other
# now set tmux to trigger on `alert-bell` actions
set-hook -g alert-bell 'run-shell "\
apprise \
--title \"tmux finished on #{host}\" \
--body \"in session #{session_name} window #{window_index}:#{window_name}\" \
discord://webhook_id/webhook_token \
slack://TokenA/TokenB/TokenC/Channel \
twilio://AccountSid:AuthToken@FromPhoneNo"