Add Discord Notifications to Backup Script #634
Merged
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
|
@dan3805 |
|
|
github-actions
bot
force-pushed
the
backup-script-discord-webhook
branch
from
365e86f
to
5757dc4
Compare
github-actions
bot
force-pushed
the
backup-script-discord-webhook
branch
2 times, most recently
from
eb797d5
to
23c6561
Compare
github-actions
bot
force-pushed
the
backup-script-discord-webhook
branch
2 times, most recently
from
707c1fc
to
a4216f1
Compare
In this commit, we enhanced the Docker backup script by integrating it with Discord notifications. The notifications are sent through a Discord webhook which enables real-time updates about the backup process. Here are the key changes made: Discord Webhook Integration: Added a Discord webhook at the end of the backup process for each Docker container. This webhook sends a message to the specified Discord channel when a backup has been completed. Dynamic Messages: The Discord messages are dynamically generated to include the name of the Docker container (ARCHIVE), the folder where the backup is stored (STORAGE), and the current timestamp when the backup was completed. Improved Tracking: With these notifications, users can monitor the progress of the backup process in real-time and can immediately know if a backup has been successfully completed or if there are issues that need to be addressed. This feature adds a new layer of visibility to the backup process and makes it easier for users to manage their Docker containers. Please ensure to replace the placeholder "[Your Discord Webhook URL Here]" with your actual Discord webhook URL to make use of this feature. Remember to keep this script secure as it contains sensitive information like your Discord Webhook URL. The script must not be shared publicly or with untrusted parties to prevent misuse. The changes are designed to improve user experience and provide an efficient way to keep track of Docker backups. As always, we appreciate any feedback or suggestions for further improvements. Signed-off-by: DoCtEuR3805 | FRENCH-QC <35934387+dan3805@users.noreply.github.com>
github-actions
bot
force-pushed
the
backup-script-discord-webhook
branch
from
3e18d46
to
08c3067
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.
In this commit, we enhanced the Docker backup script by integrating it with Discord notifications. The notifications are sent through a Discord webhook which enables real-time updates about the backup process.
Here are the key changes made:
Discord Webhook Integration: Added a Discord webhook at the end of the backup process for each Docker container. This webhook sends a message to the specified Discord channel when a backup has been completed.
Dynamic Messages: The Discord messages are dynamically generated to include the name of the Docker container (ARCHIVE), the folder where the backup is stored (STORAGE), and the current timestamp when the backup was completed.
Improved Tracking: With these notifications, users can monitor the progress of the backup process in real-time and can immediately know if a backup has been successfully completed or if there are issues that need to be addressed.
This feature adds a new layer of visibility to the backup process and makes it easier for users to manage their Docker containers.
Please ensure to add on the line WEBHOOK_URL="" your actual Discord webhook URL to make use of this feature.
Remember to keep this script secure as it contains sensitive information like your Discord Webhook URL. The script must not be shared publicly or with untrusted parties to prevent misuse.
The changes are designed to improve user experience and provide an efficient way
to keep track of Docker backups. As always, we appreciate any feedback or suggestions for further improvements.