Extend `lbcblocknotify` to support custom command and multiple destinations. #79

New issue

Closed

opened 2022-08-06 00:28:46 +02:00 by roylee17 · 1 comment

roylee17 commented

2022-08-06 00:28:46 +02:00

(Migrated from github.com)

So far, the users of the lbcdblocknotify programs are predominantly mining pools. For reliability, some pools have multiple instances of backend and frontend services that all act upon the notification. In this case, users have to set up multiple instances of lbcdblocknotify

It is desired to have multiple subscribers for the notification where each of them can customize their command and end points.

So far, the users of the `lbcdblocknotify` programs are predominantly mining pools. For reliability, some pools have multiple instances of backend and frontend services that all act upon the notification. In this case, users have to set up multiple instances of **lbcdblocknotify** It is desired to have multiple subscribers for the notification where each of them can customize their command and end points.

roylee17 commented

2022-08-08 08:58:52 +02:00

(Migrated from github.com)

Support running a custom command with '--run' seems enough as user can wrap the rest in their custom script.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbcd#79

No description provided.

Extend lbcblocknotify to support custom command and multiple destinations. #79

Extend `lbcblocknotify` to support custom command and multiple destinations. #79