https://319-merge.resticprofile.pages.dev/tags/v0.18.0/index.htmlRecent content in v0.18.0 on resticprofileHugo -- gohugo.ioen-gbMon, 16 May 2022 19:46:52 +0100https://319-merge.resticprofile.pages.dev/configuration/include/index.htmlMon, 02 May 2022 20:00:00 +0200https://319-merge.resticprofile.pages.dev/configuration/include/index.htmlThe configuration may be split into multiple files by adding includes = "glob-pattern" to the main configuration file. E.g. the following profiles.conf loads configurations from conf.d and profiles.d: ​ toml yaml hcl json version = "1" # Includes includes = ["conf.d/*.conf", "profiles.d/*.yaml", "profiles.d/*.toml"] # Defaults [global] initialize = true version: "1" includes: - "conf.d/*.conf" - "profiles.d/*.yaml" - "profiles.d/*.toml" global: initialize: true includes = ["conf.d/*.conf", "profiles.d/*.yaml", "profiles.d/*.toml"] global { initialize = true } { "version": "1", "includes": [ "conf.https://319-merge.resticprofile.pages.dev/configuration/copy/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://319-merge.resticprofile.pages.dev/configuration/copy/index.htmlSpecial case for the copy command section The copy command needs two repositories (and quite likely 2 different set of keys). You can configure a copy section like this: ​ toml yaml hcl version = "1" [default] initialize = false repository = "/backup/original" password-file = "key" [default.copy] initialize = true repository = "/backup/copy" password-file = "other_key" version: "1" default: initialize: false repository: "/backup/original" password-file: key copy: initialize: true repository: "/backup/copy" password-file: other_key default { initialize = false repository = "/backup/original" password-file = "key" copy = { initialize = true repository = "/backup/copy" password-file = "other_key" } } You will note that the secondary repository doesn’t need to have a 2 behind its flags (repository2, password-file2, etc.https://319-merge.resticprofile.pages.dev/configuration/http_hooks/index.htmlMon, 16 May 2022 19:46:52 +0100https://319-merge.resticprofile.pages.dev/configuration/http_hooks/index.htmlSend HTTP messages before and after a job As well as being able to run shell commands, you can now send HTTP messages before, after (success or failure) running a restic command. The sections that allow sending HTTP hooks are: backup copy check forget prune Tip You might notice that’s the same sections that can also be scheduled Each of these commands can send 4 different types of hooks: send-before send-after send-after-fail send-finally The configuration is the same for each of these 4 types of hooks:https://319-merge.resticprofile.pages.dev/installation/docker/index.htmlSat, 23 Apr 2022 23:58:56 +0100https://319-merge.resticprofile.pages.dev/installation/docker/index.htmlUsing resticprofile from a docker image You can run resticprofile inside a docker container. It is probably the easiest way to install resticprofile (and restic at the same time) and keep it updated. But be aware that you will need to mount your backup source (and destination if it’s local) as a docker volume. Depending on your operating system, the backup might be slower. Volumes mounted on a mac OS host are well known for being quite slow.