1
0
Fork 0
mirror of https://github.com/Luzifer/duplicity-backup.git synced 2024-11-08 15:10:06 +00:00
Wrapper to execute a duplicity backup using a configuration file
Find a file
Knut Ahlers f726880d90
Improve code quality, update deps
Signed-off-by: Knut Ahlers <knut@ahlers.me>
2023-08-21 13:53:01 +02:00
.gitignore Initial version 2016-05-22 15:04:37 +02:00
.repo-runner.yaml Update build system / GH publish 2018-10-08 15:16:12 +02:00
.travis.yml Test on latest two Go versions 2018-10-08 15:16:44 +02:00
bufferedLineWriter.go Lint: Handle several linter errors 2018-10-08 16:06:28 +02:00
config.example.yaml Implemented notifications 2016-05-23 10:41:20 +02:00
configfile.go Improve code quality, update deps 2023-08-21 13:53:01 +02:00
configfile_test.go Improve code quality, update deps 2023-08-21 13:53:01 +02:00
duplicity_backup_suite_test.go Improve code quality, update deps 2023-08-21 13:53:01 +02:00
go.mod Improve code quality, update deps 2023-08-21 13:53:01 +02:00
go.sum Improve code quality, update deps 2023-08-21 13:53:01 +02:00
help.txt Added "list-changed-files" command 2016-06-26 01:33:54 +02:00
History.md prepare release v0.10.0 2019-08-17 00:19:54 +02:00
LICENSE Fix license text 2018-10-08 15:08:11 +02:00
main.go Improve code quality, update deps 2023-08-21 13:53:01 +02:00
Makefile Improve code quality, update deps 2023-08-21 13:53:01 +02:00
notification.go Improve code quality, update deps 2023-08-21 13:53:01 +02:00
README.md Update README buttons 2018-10-08 15:08:58 +02:00

Go Report Card Build Status

Luzifer / duplicity-backup

duplicity-backup is a wrapper to execute a duplicity backup using a configuration file. It is designed to simplify handling backups on and restores from remote targets. All information required for the backup is set using the configuration file. Also the wrapper notifies targets (slack / mondash) about successful and failed backups.

Using without writing passwords to disk

Starting with version v0.7.0 the duplicity-backup wrapper supports reading variables from the environment instead of writing the secrets to your disk. In every section of the file you can use the function {{env "encrypt-password"}} to read configuration options from the environment. As an example you could utilize vault2env to set those variables from a Vault instance:

# vault write /secret/backups/mybackup encrypt-password=bVFq5jdyvkHD6VCvSQUY
Success! Data written to: secret/backups/mybackup

# cat ~/.duplicity.yaml
[...]
encryption:
  enable: true
  passphrase: {{env `encrypt-password`}}
[...]

# vault2env /secret/backups/mybackup -- duplicity-backup -f ~/.duplicity.yaml backup
(2016-06-25 15:07:06) ++++ duplicity-backup v0.7.0 started with command 'backup'
[...]