[GH-ISSUE #31] Add push notifications #11

New issue

Closed

opened 2026-10-13 19:45:45 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-13 19:45:45 +00:00

Owner

Originally created by @DSilence on GitHub (Dec 13, 2015).
Original GitHub issue: https://github.com/werwolfby/monitorrent/issues/31

Originally assigned to: @DSilence on GitHub.

The following push notification plugins should be implemented:

pushbullet
pushover
pushall
telegram bot
email

Also need to discuss actual notification usage, e.g. server events and stuff

Originally created by @DSilence on GitHub (Dec 13, 2015). Original GitHub issue: https://github.com/werwolfby/monitorrent/issues/31 Originally assigned to: @DSilence on GitHub. The following push notification plugins should be implemented: - pushbullet - pushover - pushall - telegram bot - email Also need to discuss actual notification usage, e.g. server events and stuff

bsakaguchi closed this issue

2026-10-13 19:45:46 +00:00

bsakaguchi commented

2026-10-13 19:45:47 +00:00

Author

Owner

@DSilence commented on GitHub (Mar 20, 2016):

The following are notifiers parameters:
Pushall:

UserId.
Access token.

Pushbullet:

Access token.

Pushover:

UserId.
Access token.

Telegram:

Chat id.
Access token.

Email:

SMTP Host.
SMTP Port.
SMTP Login.
SMTP Password.
To address.
Connection timeout in second (not necessary, 30 by default).
Connection security: SSL, TLS or Empty

@DSilence commented on GitHub (Mar 20, 2016): The following are notifiers parameters: Pushall: 1. UserId. 2. Access token. Pushbullet: 1. Access token. Pushover: 1. UserId. 2. Access token. Telegram: 1. Chat id. 2. Access token. Email: 1. SMTP Host. 2. SMTP Port. 3. SMTP Login. 4. SMTP Password. 5. To address. 6. Connection timeout in second (not necessary, 30 by default). 7. Connection security: SSL, TLS or Empty

bsakaguchi referenced this issue

2026-10-13 19:56:19 +00:00

[PR #11] [CLOSED] Changed: switched from using application to blueprint, to make it eas… #340