feat: add resend notification functionality#3512
Merged
Siumauricio merged 14 commits intoDokploy:canaryfrom Feb 5, 2026
Merged
feat: add resend notification functionality#3512Siumauricio merged 14 commits intoDokploy:canaryfrom
Siumauricio merged 14 commits intoDokploy:canaryfrom
Conversation
- 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.
Contributor
|
Can you fix the conflicts? |
- 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 |
- Deleted SQL files '0136_tidy_puff_adder.sql' and '0137_worried_shriek.sql' as they are no longer needed. - Updated the journal and removed references to the deleted SQL files. - Cleaned up the corresponding snapshot JSON files to maintain a tidy project structure.
- Added fast-sha256@1.3.0 and uuid@10.0.0 with their respective integrity resolutions. - Updated snapshots to include the new package entries.
This reverts commit d77c562. # Conflicts: # apps/dokploy/drizzle/meta/0137_snapshot.json # apps/dokploy/drizzle/meta/_journal.json
- Deleted the '0137_worried_shriek.sql' file as it is no longer needed. - Updated the journal to remove references to the deleted SQL file. - Removed the corresponding snapshot JSON file to maintain a tidy project structure.
- Introduced a new notification type 'pushover' to the database. - Created a new table 'pushover' with relevant fields for notification management. - Updated the 'notification' table to include a foreign key reference to 'pushoverId' for enhanced notification handling. - Added corresponding snapshot and journal entries to reflect these changes.
- Introduced a new notification type 'resend' to the database. - Created a new table 'resend' with fields for managing resend notifications. - Updated the 'notification' table to include a foreign key reference to 'resendId'. - Added corresponding snapshot and journal entries to reflect these changes.
Contributor
Author
My pleasure |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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)