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 5f76e7451c
Fix license text
Signed-off-by: Knut Ahlers <knut@ahlers.me>
2018-10-08 15:08:11 +02:00
Godeps Send notifications only on some commands 2016-05-23 11:54:45 +02:00
vendor Added missing vendored packages 2016-05-23 12:19:19 +02:00
.gitignore Initial version 2016-05-22 15:04:37 +02:00
.gobuilder.yml Added version writing to install / gobuilder 2016-05-23 13:20:01 +02:00
.repo-runner.yaml Push releases to Github 2016-10-28 14:54:35 +02:00
.travis.yml Do not test on go1.5 (we're using go1.6 vendoring) 2016-05-22 15:20:01 +02:00
bindata.go Added "list-changed-files" command 2016-06-26 01:33:54 +02:00
bufferedLineWriter.go Fix: Unexported constructor for private struct 2016-05-23 16:04:50 +02:00
config.example.yaml Implemented notifications 2016-05-23 10:41:20 +02:00
configfile.go Added "list-changed-files" command 2016-06-26 01:33:54 +02:00
configfile_test.go Fix test after API change 2016-06-26 10:52:30 +02:00
duplicity_backup_suite_test.go Initial version 2016-05-22 15:04:37 +02:00
help.txt Added "list-changed-files" command 2016-06-26 01:33:54 +02:00
History.md prepare release v0.8.2 2016-10-28 14:55:26 +02:00
LICENSE Fix license text 2018-10-08 15:08:11 +02:00
main.go Added "list-changed-files" command 2016-06-26 01:33:54 +02:00
Makefile Push releases to Github 2016-10-28 14:54:35 +02:00
notification.go Send notifications only on some commands 2016-05-23 11:54:45 +02:00
publish.sh Push releases to Github 2016-10-28 14:54:35 +02:00
README.md Remove GoBuild button as releases are now sent to Github 2016-10-28 14:54:59 +02:00

License: Apache v2.0 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'
[...]