Wrapper to execute a duplicity backup using a configuration file
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
vendor
.gitignore
.repo-runner.yaml
.travis.yml
Gopkg.lock
Gopkg.toml
History.md
LICENSE
Makefile
README.md
bindata.go
bufferedLineWriter.go
config.example.yaml
configfile.go
configfile_test.go
duplicity_backup_suite_test.go
help.txt
main.go
notification.go

README.md

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'
[...]