We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dollar templating
Right now the after-backup commands are written completely by the user.
after-backup
But we should provide some resolving of the commands using demp.
demp
Let me explain
storeDir = "some-system-path" after-backup = [ "tar -czvf backup.tar.gz <the-full-fucking-path>" ]
What if we support dollar templating like we use for groom. Meaning
groom
storeDir = "some-system-path" after-backup = [ "tar -czvf backup.tar.gz $storeDir" ]
It makes it easier for the user to build upon complex commands. Like
storeDir = "some-system-path" after-backup = [ "tar -C $storeDir -czvf backup.tar.gz $storeDir", "scp ${storeDir}/backup.tar.gz <some-server>", # Either delete the `backup.tar.gz` or not, dotback will work. "rm ${storeDir}/backup.tar.gz" ]
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Right now the
after-backup
commands are written completely by the user.But we should provide some resolving of the commands using
demp
.Let me explain
What if we support
dollar templating
like we use forgroom
.Meaning
It makes it easier for the user to build upon complex commands.
Like
The text was updated successfully, but these errors were encountered: