feat(notification): send notification when dokploy update is available#2968
Open
Bima42 wants to merge 21 commits intoDokploy:canaryfrom
Open
feat(notification): send notification when dokploy update is available#2968Bima42 wants to merge 21 commits intoDokploy:canaryfrom
Bima42 wants to merge 21 commits intoDokploy:canaryfrom
Conversation
Bima42
force-pushed
the
feat/2663-notification-for-dokploy-update
branch
from
a9ce666 to
b633836
Compare
# Conflicts: # apps/dokploy/drizzle/meta/0121_snapshot.json # apps/dokploy/drizzle/meta/_journal.json
# Conflicts: # apps/dokploy/drizzle/meta/0125_snapshot.json # apps/dokploy/drizzle/meta/_journal.json # packages/server/src/utils/backups/index.ts
Contributor
Author
|
Any news on this PR @Siumauricio ? Should I continue to keep it up to date? |
dosubot
bot
added
the
size:XL
…cker configurations - Updated Node.js version from 20.16.0 to 24.4.0 in .nvmrc, Dockerfiles, and package.json. - Upgraded pnpm from 9.12.0 to 10.22.0. - Added `ignoreUnknown` option in biome.json for better file handling. - Improved CONTRIBUTING.md with clearer guidelines and added a section on important considerations for pull requests. - Updated Dockerfile configurations to use the latest versions of dependencies and added health checks. - Introduced LICENSE_PROPRIETARY.md for proprietary licensing details. - Enhanced README.md to reflect new features and removed outdated sponsor information. - Added devcontainer configuration for streamlined development setup. - Updated OpenAPI documentation and added new API endpoints for deployment job management. - Refactored API service and schema to support new functionalities.
…cker configurations - Updated Node.js version from 20.16.0 to 24.4.0 across various files including Dockerfiles and package.json. - Upgraded pnpm from 9.12.0 to 10.22.0. - Added new configuration options in biome.json and improved the CONTRIBUTING.md file for clarity. - Introduced a new LICENSE_PROPRIETARY.md file to clarify licensing terms. - Enhanced Dockerfile configurations for better performance and added health checks. - Updated OpenAPI documentation and added new API endpoints for deployment job management. - Improved the README.md by adding new features and removing outdated sponsor information. - Added devcontainer configuration for easier development setup.
dosubot
bot
added
size:XXL
dosubot
bot
added
size:XL
Bima42
force-pushed
the
feat/2663-notification-for-dokploy-update
branch
from
dc347d1 to
9fcb076
Compare
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?
This PR implements notification support for Dokploy updates as requested in the issue.
Only available for self hosted version.
Changes Made:
Added "Dokploy Update" notification action to the notification modal, allowing all notification providers (Discord, Slack, Telegram, Email, etc.) to subscribe to update alerts, if Dokploy is self hosted
Implemented a background cron job that runs every 10 minutes in production to check for available updates using the existing
getUpdateDatasystemTrack the last version notified in
organizationmodel usinglastNotifiedUpdateVersionTesting
initCronJobin dev envIssues related (if applicable)
closes #2663
Screenshots (if applicable)
UI
Notifications