Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
roylee17 opened this issue Aug 5, 2022 · 1 comment · Fixed by #80
Closed

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

roylee17 opened this issue Aug 5, 2022 · 1 comment · Fixed by #80
Assignees
Labels
mining Mining (including pool) related issues ux User experience

Comments

@roylee17
Copy link
Collaborator

roylee17 commented Aug 5, 2022

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 roylee17 added ux User experience mining Mining (including pool) related issues labels Aug 5, 2022
@roylee17 roylee17 self-assigned this Aug 5, 2022
@roylee17 roylee17 changed the title Extend **lbcblocknotify** to support custom command and multiple destinations. Extend lbcblocknotify to support custom command and multiple destinations. Aug 5, 2022
@roylee17
Copy link
Collaborator Author

roylee17 commented Aug 8, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mining Mining (including pool) related issues ux User experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant