From 584e0972fe0b86af70d41b4401a8063cfe1b18a1 Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Sat, 16 Nov 2019 22:32:15 -0500 Subject: [PATCH] Updated CLI_Usage (markdown) --- CLI_Usage.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/CLI_Usage.md b/CLI_Usage.md index c37d2b3..69256f5 100644 --- a/CLI_Usage.md +++ b/CLI_Usage.md @@ -56,6 +56,27 @@ With default configuration file(s) in place, reference to the Apprise CLI gets e apprise --body="Notify all of my services" ``` +#### Attachment Support +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: +```bash +# 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 --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.jpg +``` + +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: +```bash +# A web-based attachment: +apprise --title="A Great Github Cheatsheet" --body="see attached" \ + --attach=https://github.github.com/training-kit/downloads/github-git-cheat-sheet.pdf +``` + ### :label: Leverage Tagging 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. * :inbox_tray: Maybe you have special notifications that only fire when a download completed.