ssup!
ssup is a simple cross-platform tool to send notifications via cli to local system or telegram.
It can also be used to get alerted after a long-running (or otherwise) command finishes. This can be used either by specifying the command at the end of the ssup command, or by chaining ssup with other commands. See the examples/CLI options below for more.
Examples
```
Send a notification to local system
$ ssup -m "Hello world!"
Send a notification to telegram
$ export SSUPTGBOT_TOKEN=
$ ssup -m "Hello world!" -d telegram -c
Run a custom command and send notification after it finishes. Advantage of this is that ssup will also report whether command was successful or not.
$ ssup -m "Hello world!" sleep 5
Alternate ways to run a custom command and send notification after it finishes
$ sleep 5; ssup -m "Hello world!" # Always send notification
$ sleep 5 && ssup -m "Hello world!" # Send notification only on success
$ sleep 5 || ssup -m "Hello world!" # Send notification only on failure
```
Currently supported platforms
Currently supported architectures
- x86_64
- aarch64 (e.g. Raspberry Pi 4b, Apple M1)
Currently supported notification targets
- local (i.e. System notifications, this is provided by the great
notifica crate)
- telegram
CLI Options
```
█████ █████ █████ ████ ████████
███░░ ███░░ ░░███ ░███ ░░███░░███
░░░█████ ░█████ ░███ ░███ ░███ ░███
░░░░███░░░░███ ░███ ░███ ░███ ░███
██████ ██████ ░░████████ ░███████
░░░░░░░ ░░░░░ ░░░░░░░░ ░███░░░
░███
█████
░░░░░
ssup 0.3.3 - Shantanu Goel
A utility to send notifications to local system or telegram
USAGE:
ssup [OPTIONS] --message [command]
ARGS:
Specify a command/executable to run and notify when it finishes
FLAGS:
-h, --help Prints help information
-V, --version Prints version information
OPTIONS:
-t, --title
Optional title for the notification [default: Ssup!]
-m, --message <message> Notify with this message
-d, --destination <destination> Choose where to send the notification to [default: local] [possible values: local, telegram]
--chat-id <chat-id> {Telegram specific option} Chat id to which notification should be sent
--bot-token <bot-token> {Telegram specific option } Optionally specify Telegram bot token in command instead of reading from env
```</p>
<h2>Telegram Usage</h2>
<ul>
<li>Create a bot and get a bot token following <a href="https://core.telegram.org/bots#6-botfather">these instructions</a></li>
<li>Send a message to your bot from the telegram account on which you want to receive notifications</li>
<li>Get the chat id by running the below command
<ul>
<li><code>curl https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/getUpdates | jq .message.chat.id</code></li>
<li>Replace <code>$TELEGRAM_BOT_TOKEN</code> by the token value that you got in step 1</li>
<li>You may need to install <code>curl</code> and <code>jq</code> if you don't have them already</li>
<li>Alternatively, you can enter this url in your browser <code>https://api.telegram.org/bot$TELEGRAM_BOT_TOKEN/getUpdates</code> and search for <code>id:</code> to get the value</li>
</ul></li>
<li>Use the bot token and chat id values in the CLI options given above. </li>
</ul>
<h1>Building</h1>
<p>For linux platforms, this crate has a native dependency on libdbus, so you'd need to install a corresponding package (e.g. libdbus-1-dev on debian/ubuntu) before trying to compile it.</p>
<h1>TODO</h1>
<ul>
<li>[ ] Add support for 32b (aarch32 and i686/386) linux builds</li>
<li>[ ] Add custom webhook destination</li>
<li>[ ] Add tests</li>
<li>[ ] ?</li>
</ul>
</body></html>