mirror of https://github.com/caronc/apprise
Chris Caron
parent
c88c64aad1
commit
808497b58a
|
|
@ -26,7 +26,7 @@
|
|||
# POSSIBILITY OF SUCH DAMAGE.
|
||||
|
||||
__title__ = "Apprise"
|
||||
__version__ = "1.9.3"
|
||||
__version__ = "1.9.4"
|
||||
__author__ = "Chris Caron"
|
||||
__license__ = "BSD 2-Clause"
|
||||
__copywrite__ = "Copyright (C) 2025 Chris Caron <lead2gold@gmail.com>"
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -1,6 +1,6 @@
|
|||
.\" generated with Ronn-NG/v0.10.1
|
||||
.\" http://github.com/apjanke/ronn-ng/tree/0.10.1
|
||||
.TH "APPRISE" "1" "July 2025" "Chris Caron <lead2gold@gmail.com>"
|
||||
.\" generated with Ronn-NG/v0.9.1
|
||||
.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
|
||||
.TH "APPRISE" "1" "August 2025" "Chris Caron <lead2gold@gmail.com>"
|
||||
.SH "NAME"
|
||||
\fBapprise\fR \- Push Notifications that work with just about every platform!
|
||||
.SH "SYNOPSIS"
|
||||
|
|
@ -10,15 +10,15 @@
|
|||
.br
|
||||
.SH "DESCRIPTION"
|
||||
\fBApprise\fR allows you to send a notification to \fIalmost all\fR of the most popular notification services available to us today such as: Discord, Telegram, Pushbullet, Slack, Twitter, etc\.
|
||||
.IP "\(bu" 4
|
||||
.IP "\[ci]" 4
|
||||
One notification library to rule them all\.
|
||||
.IP "\(bu" 4
|
||||
.IP "\[ci]" 4
|
||||
A common and intuitive notification syntax\.
|
||||
.IP "\(bu" 4
|
||||
.IP "\[ci]" 4
|
||||
Supports the handling of images (to the notification services that will accept them)\.
|
||||
.IP "\(bu" 4
|
||||
It's incredibly lightweight\.
|
||||
.IP "\(bu" 4
|
||||
.IP "\[ci]" 4
|
||||
It\'s incredibly lightweight\.
|
||||
.IP "\[ci]" 4
|
||||
Amazing response times because all messages sent asynchronously\.
|
||||
.IP "" 0
|
||||
.SH "OPTIONS"
|
||||
|
|
@ -97,17 +97,17 @@ The \fBstorage\fR action has the following sub actions:
|
|||
\fBclean\fR: Removes all persistent storage reguardless of age\.
|
||||
.SH "EXIT STATUS"
|
||||
\fBapprise\fR exits with a status of:
|
||||
.IP "\(bu" 4
|
||||
.IP "\[ci]" 4
|
||||
\fB0\fR if all of the notifications were sent successfully\.
|
||||
.IP "\(bu" 4
|
||||
.IP "\[ci]" 4
|
||||
\fB1\fR if one or more notifications could not be sent\.
|
||||
.IP "\(bu" 4
|
||||
.IP "\[ci]" 4
|
||||
\fB2\fR if there was an error specified on the command line such as not providing an valid argument\.
|
||||
.IP "\(bu" 4
|
||||
.IP "\[ci]" 4
|
||||
\fB3\fR if there was one or more Apprise Service URLs successfully loaded but none could be notified due to user filtering (via tags)\.
|
||||
.IP "" 0
|
||||
.SH "SERVICE URLS"
|
||||
There are to many service URL and combinations to list here\. It's best to visit the Apprise GitHub page \fIhttps://github\.com/caronc/apprise/wiki#notification\-services\fR and see what's available\.
|
||||
There are to many service URL and combinations to list here\. It\'s best to visit the Apprise GitHub page \fIhttps://github\.com/caronc/apprise/wiki#notification\-services\fR and see what\'s available\.
|
||||
.P
|
||||
The \fBenvironment variable\fR of \fBAPPRISE_URLS\fR (comma/space delimited) can be specified to provide the default set of URLs you wish to notify if none are otherwise specified\.
|
||||
.SH "EXAMPLES"
|
||||
|
|
@ -120,7 +120,7 @@ $ apprise \-vv \-t "my title" \-b "my notification body" \e
|
|||
.fi
|
||||
.IP "" 0
|
||||
.P
|
||||
If you don't specify a \fB\-\-body\fR (\fB\-b\fR) then stdin is used allowing you to use the tool as part of your every day administration:
|
||||
If you don\'t specify a \fB\-\-body\fR (\fB\-b\fR) then stdin is used allowing you to use the tool as part of your every day administration:
|
||||
.IP "" 4
|
||||
.nf
|
||||
$ cat /proc/cpuinfo | apprise \-vv \-t "cpu info" \e
|
||||
|
|
@ -174,7 +174,7 @@ $ apprise storage prune \-\-storage\-prune\-days=10
|
|||
.fi
|
||||
.IP "" 0
|
||||
.SH "CUSTOM PLUGIN/NOTIFICATIONS"
|
||||
Apprise can additionally allow you to define your own custom \fBschema://\fR entries that you can trigger on and call services you've defined\.
|
||||
Apprise can additionally allow you to define your own custom \fBschema://\fR entries that you can trigger on and call services you\'ve defined\.
|
||||
.P
|
||||
By default \fBapprise\fR looks in the following local locations for custom plugin files and loads them:
|
||||
.IP "" 4
|
||||
|
|
|
|||
|
|
@ -420,7 +420,7 @@ configuration that you want and only specifically notify a subset of them:</p>
|
|||
|
||||
<ol class='man-decor man-foot man foot'>
|
||||
<li class='tl'>Chris Caron <lead2gold@gmail.com></li>
|
||||
<li class='tc'>February 2025</li>
|
||||
<li class='tc'>August 2025</li>
|
||||
<li class='tr'>apprise(1)</li>
|
||||
</ol>
|
||||
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ notification services. It supports sending alerts to platforms such as: \
|
|||
`Webex Teams`, `Workflows`, `WxPusher`, and `XBMC`.}
|
||||
|
||||
Name: python-%{pypi_name}
|
||||
Version: 1.9.3
|
||||
Version: 1.9.4
|
||||
Release: 1%{?dist}
|
||||
Summary: A simple wrapper to many popular notification services used today
|
||||
License: BSD-2-Clause
|
||||
|
|
@ -214,6 +214,9 @@ LANG=C.UTF-8 PYTHONPATH=%{buildroot}%{python3_sitelib}:%{_builddir}/%{name}-%{ve
|
|||
%{python3_sitelib}/%{pypi_name}/__pycache__/cli*.py?
|
||||
|
||||
%changelog
|
||||
* Sat Aug 2 2025 Chris Caron <lead2gold@gmail.com> - 1.9.4
|
||||
- Updated to v1.9.4
|
||||
|
||||
* Sun Mar 30 2025 Chris Caron <lead2gold@gmail.com> - 1.9.3
|
||||
- Updated to v1.9.3
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue