Repository navigation
Expand file tree
/
Copy pathconfig.example.yaml
More file actions
171 lines (150 loc) · 4.83 KB
/
Copy pathconfig.example.yaml
File metadata and controls
171 lines (150 loc) · 4.83 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
###
# Backup source
###
#
# Root of the backup to create. If no explicit excludes or includes are
# defined all files inside this directory will be backed up.
root: /home
# Hostname for notifications (if left out the hostname of the machine
# is used for this.
#hostname: mystation
###
# Backup destination
###
#
# Destination for the backup. Check the duplicity man-page for all
# possible destinations to use.
dest: s3+http://foobar-backup-bucket/backup-folder/
# Some examples of destinations usable for your backup:
#dest: ftp://user[:password]@other.host[:port]/some_dir
#dest: rsync://user@host.com[:port]//absolute_path
#dest: ssh://user[:password]@other.host[:port]/[/]some_dir
# The "ftp_password" is used for several backends despite the options
# name. You can use this option instead of passing the password in the
# `dest` parameter as that one is visible in the process list during
# the backup is running.
#ftp_password: password
###
# Amazon WebServices S3 configuration
###
#
# Uncomment the lines in this section if you're using Amazon S3
aws:
# access_key_id: foobar_aws_key_id
# secret_access_key: foobar_aws_access_key
# Without setting the storage class the standard storage is used. With
# this option you can switch to "infrequent access" (--s3-use-ia) or
# "reduced redundancy" (--s3-use-rrs) storage class.
# storage_class: --s3-use-ia
###
# Google Cloud Storage configuration
###
#
# Uncomment the lines in this section if you're using GCS
google_cloud:
# access_key_id: foobar_gcs_key_id
# secret_access_key: foobar_gcs_secret_id
###
# OpenStack Object Storage (Swift) configuration
###
#
# Uncomment the lines in this section if you're using OpenStack
swift:
# username: foobar_swift_tenant:foobar_swift_username
# password: foobar_swift_password
# auth_url: foobar_swift_authurl
# auth_version: 2
###
# Include list of directories
###
#
# Specify directories inside your `root` to backup only these ones
# You can't specify directories outside the root. If you want to backup
# all the data inside the root leave this list empty.
inclist:
- /home/myuser/projects
###
# Exclude list of directories
###
#
# Specify directories inside your `root` to exclude these ones
# You can't specify directories outside the root. If you want to backup
# all the data inside the root leave this list empty.
exclist:
- /home/muser/projects/testproject
###
# Other file selection options
###
#
# Instead managing the inclist / exclist parameters in this file you
# can write a text file containing lines with +/- patterns to include
# or exclude files and directories from the backup.
# See http://duplicity.nongnu.org/duplicity.1.html#sect9 for details
#incexcfile: /home/myuser/.config/backup-files.txt
# Exclude all device files. This can be useful for security/permissions
# reasons or if rdiff-backup is not handling device files correctly.
#excdevicefiles: true
###
# Encryption configuration
###
#
encryption:
# Enable / disable encryption of your backup. If you enable encryption
# you either need to specify a password or a GPG key.
enable: true
# If you're using a `gpg_sign_key` to sign your backup this password is
# used to unlock the GPG key. If you're not using a GPG key it is used
# to symmetrically encrypt the backup.
passphrase: foobar_gpg_passphrase
# Specify the GPG key(s) to use for encryption / signing the backup.
# You may use different keys for those tasks. If you specify a signing
# key you need to specify the password above to unlock the key.
# gpg_encryption_key: foobar_gpg_key
# gpg_sign_key: foobar_gpg_key
# If you want to hide the GPG key IDs for security reasons you can
# enable this option.
# hide_key_id: true
# You can specify the keyring which contains your above specified keys
# in case they are not present in the default keyring.
# secret_keyring: /home/myuser/.gnupg/duplicity.gpg
###
# Static backup options
###
#
# Here you can specify other options for duplicity not handled in this
# configuration file. Reference is the manpage of duplicity. Please
# ensure you're specifying the options in command array format.
static_options: ["--full-if-older-than", "14D", "--s3-use-new-style"]
###
# Backup cleanup options
###
#
cleanup:
# Chose the cleanup type and the configured value for that cleanup type:
# remove-older-than <time>
# remove-all-but-n-full <count>
# remove-all-inc-of-but-n-full <count>
# none
type: remove-all-but-n-full
value: 4
###
# Logging
###
#
# Set the directory the logs are written to
logdir: /tmp/duplicity/
###
# Nofification configuration
###
#
# Uncomment and configure your preferred notification channel
notifications:
# slack:
# hook_url: https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX
# channel: "#general"
# username: duplicity-backup
# emoji: :package:
# mondash:
# board: https://mondash.org/yourboardurl
# token: yoursecrettoken
# freshness: 3600