Update dobackup.sh to allow manual trigger #22
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
|
@peterrus is there any chance this can be added to the project? It's something I was exploring on my side, and see it as something useful |
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.
Minor change to
dobackup.shas I wanted to manually trigger the backup from outside the container.This is helpful for manual triggers but also makes it easier to test.
Currently:
entrypoint.shwrites to/home/backup/.envdobackup.shreads the env from.envwhich works but doesn't for manual triggers. This part confuses me because I don't quite get how it works currently.My change:
The README is updated as well to explain how to use this new functionality.