-
Notifications
You must be signed in to change notification settings - Fork 41
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
Email notification #433
Merged
Merged
Email notification #433
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
966a93d
to
b0b718f
Compare
Generated by E2E-Test |
b0b718f
to
e1d6719
Compare
mathiashoeld
suggested changes
Mar 10, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
important: please change all occurrences of "email" to "email address" where appropriate
blockchain/src/multichain-feed/email-notifications/notificationWatcher.js
Show resolved
Hide resolved
blockchain/src/multichain-feed/email-notifications/notificationWatcher.js
Outdated
Show resolved
Hide resolved
4cbef60
to
586a683
Compare
mathiashoeld
approved these changes
Mar 16, 2020
5b3424f
to
56dd935
Compare
The email-service starts two servers when executed Server started: - TCP Server (TCP Command Listener) All relevant hooks should be handled (currently only sendNotifications) - HTTP Server (express) All requests which modify the email database are handled
On walletnotifynew, a mutlichain runtimeparamter, a script called 'filterScript' (written in go) is executed This script checks each transaction if it's a notification_created event. If so a notification is send via tcp to the email-service. To configure te email-service connection following env vars are used: - EMAIL_HOST - EMAIL_PORT
Only show email if service available Implement un-/subscribe to the email notification
Create directory "notifications" if not exist (done by sendData as well as filterScript) Clean up windows binary files Prepared docker-compose file including email service and email database
Rename filterScript to multichain-feed Structure go code to be able to easily exand the multichain-feed with other hooks/sideEffects
Restructure filesystem improve logging
Add e2e tests for the following cases: * Email service is available * Email service is not available
56dd935
to
99b4abe
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Solution
As shown in the architecture section below, a script shall filter every transaction. The script saves the transactions with a timestamp locally as files in a notification folder.
An external process watches the notification folder and sends the user's ids via http request to the email service.
The email service creates one http server which handle:
Via env variables the email service can connect to the external SMTP-Server which actually sends the emails.
The frontend handles a user's email address in a user profile, available when clicking on the profile picture.
Architecture
Todo
Email-Service
Hook/ filterScript
Frontend
Documentation
User Guide-> email-service: Write user guide #457Closes #419
Closes #65