feat: add resend notification functionality #3512
Open
Conversation
This file contains hidden or 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
- Introduced a new notification type "resend" to the system. - Added database schema for resend notifications including fields for apiKey, fromAddress, and toAddress. - Implemented functions to create, update, and send resend notifications. - Updated notification router to handle resend notifications with appropriate API endpoints. - Enhanced existing notification services to support sending notifications via the Resend service. - Modified various notification utilities to accommodate the new resend functionality.
The profile form was sending `name` field but the database column is `firstName`. This caused the firstName to be silently ignored during updates. Changed form field and API schema to use `firstName` to match the database column.
…us-bash Fix/prevent send malicious bash
…us-bash fix(wss): add container ID validation to enhance security in WebSocke…
…us-bash feat(wss): add directory validation for WebSocket server log paths
fix: profile firstName field not updating
…domain-fail-with-only-mail fix: zod object for assign domain
…ations feat: add Pushover notification provider
Contributor
|
Can you fix the conflicts? |
chore(databases): bump default postgres version while creating to 18
…rong-when-using-remote-builder fix(application): update commit info extraction to include appName an…
…figuration in tests
…epository-as-a-provider-spaces-in-the-repo-name-break-the-repo-selection feat(bitbucket): add optional slug field for repositories and update …
…uance-broken-with-inwx chore(traefik): update Traefik version to 3.6.7 in setup scripts
- Introduced a new notification type "resend" to the system. - Added database schema for resend notifications including fields for apiKey, fromAddress, and toAddress. - Implemented functions to create, update, and send resend notifications. - Updated notification router to handle resend notifications with appropriate API endpoints. - Enhanced existing notification services to support sending notifications via the Resend service. - Modified various notification utilities to accommodate the new resend functionality.
…m/mhbdev/dokploy into resend-provider-for-notifications
Contributor
Author
Done |
- Updated the exports in the swarm forms index to include LabelsForm and ModeForm while ensuring RestartPolicyForm and UpdateConfigForm are correctly exported. - Removed the obsolete SQL file '0135_illegal_magik.sql' and its references from the journal. - Deleted the associated snapshot JSON file to clean up unused database schema definitions.
Contributor
|
Can you create the docs for this new notification provider? https://github.com/Dokploy/website/pulls, similar to this recently notification provider added #3512 |
Contributor
Author
I made a PR over there Dokploy/website#120 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
What is this PR about?
Checklist
Before submitting this PR, please make sure that:
canarybranch.Issues related (if applicable)
closes #3511
Screenshots (if applicable)