Where Does resticprofile Store Its Config?
resticprofile reads profiles.yaml style files you place yourself. It checks the current folder, then your home directory, then -c paths.
Last updated
resticprofile has no fixed home. It looks for profiles.yaml (or .toml, .json, .yaml, .hcl equivalents) in the current directory first, then ~/profiles.yaml in your home folder. Anything else needs resticprofile -c /path/to/file on every command. Schedules you install inherit that path, so pick a permanent home before scheduling.
The file holds backup profiles, retention blocks, check hooks, and schedule stanzas. Password files and repositories stay outside it by reference, which keeps secrets out of the YAML when you use password-file paths. Version the profiles file in dotfiles; guard the password files separately. The status file and Prometheus outputs land wherever the profile points them.
Where resticprofile stores this, by platform
~/profiles.yaml
Default search: current directory, then the home folder. Any format works (YAML, TOML, JSON, HCL). Schedules bake in the path, so move the file before running schedule install.
%USERPROFILE%\profiles.yaml
Same search order under the Windows user profile. Schedules register with Task Scheduler, and the -c path must stay valid for the task account. Quote paths with spaces in scheduled commands.
Frequently asked questions
how do i use a custom resticprofile filename
Pass -c with the path every time, or keep the default name profiles.yaml in the current or home directory. Any other filename requires the flag on each run, including scheduled jobs.
why use resticprofile instead of plain restic
Plain restic has no config file concept, so every flag must be repeated per invocation. resticprofile adds the file layer: named profiles, groups, schedules, and hooks that plain restic cannot express.
Notice an outdated path? Let us know.